LATEST-IS naming

LATEST-IS naming

[Randy.Dunlap]

Hi Stephen,

With the patch-vXYZ-next-datestamp.{gz,bz2} naming, having a file
named LATEST-IS-next-datestamp doesn't help scripts fill in the
vXYZ part of the patch filename.  Would it be possible/feasible
for the LATEST-IS file to have content to tell what the patch
file applies to, like:
v2.6.26-rc2

or just the full vXYZ[-rc] info in the LATEST-IS filename.

If not, do you have other suggestions/preferences?

Obviously I can get around this problem, but some direct version-datestamp
info would be helpful.

-- 
~Randy

Re: LATEST-IS naming

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 759 bytes --]

Hi Randy,

On Thu, 15 May 2008 15:03:54 -0700 (PDT) "Randy.Dunlap" <rdunlap@xenotime.net> wrote:
>
> With the patch-vXYZ-next-datestamp.{gz,bz2} naming, having a file
> named LATEST-IS-next-datestamp doesn't help scripts fill in the
> vXYZ part of the patch filename.  Would it be possible/feasible
> for the LATEST-IS file to have content to tell what the patch
> file applies to, like:
> v2.6.26-rc2

OK, I have done that for now.  I may start also making patches against
the most recent -git snapshot in which case I will put that name in the
LATEST file as well.

I will stop making full tarballs tomorrow.  Unless someone screams.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]