linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: linux-next@vger.kernel.org
Subject: LATEST-IS naming
Date: Thu, 15 May 2008 15:03:54 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0805151457570.16405@shark.he.net> (raw)

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

             reply	other threads:[~2008-05-15 22:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15 22:03 Randy.Dunlap [this message]
2008-05-19  7:08 ` LATEST-IS naming Stephen Rothwell

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=Pine.LNX.4.64.0805151457570.16405@shark.he.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-next@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).