From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [RFC PATCH 1/3] imx-uuc: new package
Date: Thu, 26 Mar 2020 17:23:15 +0100 [thread overview]
Message-ID: <20200326162315.GB20273@pengutronix.de> (raw)
In-Reply-To: <7edea84709a29d09fa4e779cec673d8321453aea.camel@diehl.com>
On Thu, Mar 26, 2020 at 09:03:58AM +0000, Denis Osterland-Heim wrote:
> Am Mittwoch, den 25.03.2020, 21:40 +0100 schrieb Roland Hieber:
> > On Wed, Mar 25, 2020 at 07:52:54PM +0100, Roland Hieber wrote:
> > > Nitpick: I don't know how picky opkg-based systems are with having
> > > monotonically increasing version numbers, but in case someone uses them
> > > to update software in the field, you could make them happy by providing
> > > a fake 'git describe' tag as a version:
> > >
> > > IMX_UUC_VERSION := 0.0-1-gd6afb27e55d73d7ad08cd2dd51c784d8ec9694dc
> > >
> > > and then increase the -1 every time for a version bump. This way git
> > > can extract the commit ID from the version info and opkg versions are
> > > increasing monotonically. The MD5 will be different though.
> Cool. I will apply.
Please use the Date of the Last commit. Also: github can produce stable
tarballs for any commit. Take a look at how this is handled in glslang.make
for example.
Michael
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2020-03-26 16:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 14:53 [ptxdist] [RFC PATCH 0/3] Freescale/NXP i.MX mfgtools 3.0 Denis Osterland-Heim
2020-03-24 14:53 ` [ptxdist] [RFC PATCH 2/3] host-libzip: new package Denis Osterland-Heim
2020-03-24 14:53 ` [ptxdist] [RFC PATCH 3/3] host-mfgtools: " Denis Osterland-Heim
2020-03-25 18:33 ` Roland Hieber
2020-03-26 8:28 ` Denis Osterland-Heim
2020-03-26 16:16 ` Michael Olbrich
2020-03-26 16:25 ` Denis Osterland-Heim
2020-03-24 14:53 ` [ptxdist] [RFC PATCH 1/3] imx-uuc: " Denis Osterland-Heim
2020-03-25 18:43 ` Roland Hieber
2020-03-25 18:52 ` Roland Hieber
2020-03-25 20:40 ` Roland Hieber
2020-03-26 9:03 ` Denis Osterland-Heim
2020-03-26 9:47 ` rhi
2020-03-26 16:23 ` Michael Olbrich [this message]
2020-03-26 16:32 ` Denis Osterland-Heim
2020-03-26 9:59 ` Guillermo Rodriguez Garcia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200326162315.GB20273@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox