Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@jdub.homelinux.org>
To: Dave Jones <davej@redhat.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Official releases?
Date: Tue, 31 Oct 2006 12:19:21 -0600	[thread overview]
Message-ID: <1162318761.3785.3.camel@zod.rchland.ibm.com> (raw)
In-Reply-To: <20061031170824.GC23354@redhat.com>

On Tue, 2006-10-31 at 12:08 -0500, Dave Jones wrote:
> On Tue, Oct 31, 2006 at 09:03:45AM -0600, Josh Boyer wrote:
>  > Howdy,
>  > 
>  > I'm just curious if anyone is ever really going to do an "official"
>  > release of sparse.  We've got daily snapshots provided by Dave Jones,
>  > and git of course, but will an official release tarball with shiny
>  > version numbers and everything be created?
>  > 
>  > The only reason I ask is because it makes packaging sparse a bit easier
>  > to some degree.
> 
> Well, all you need from a version number is a monotonically increasing
> number right?  You could munge the daily snapshot dates into same.

Yes, but you don't keep them all laying around forever.  You keep about
a week's worth right?

So if one were to package say sparse-2006-10-25.tar.gz, it'll disappear
in a week.  Makes it hard to verify those against the upstream tarball
when the tarball no longer exists :).

> It's not as 'pretty' as a real version number, but it works with
> minimal effort on behalf of Linus.

Yeah, I know.  It's not a big deal.  I was just curious if something
like an official release was ever even planned or not.

josh

  reply	other threads:[~2006-10-31 18:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-31 15:03 Official releases? Josh Boyer
2006-10-31 17:08 ` Dave Jones
2006-10-31 18:19   ` Josh Boyer [this message]
2006-10-31 18:37     ` Linus Torvalds
2006-10-31 20:36 ` Josh Triplett
2006-10-31 20:45   ` Josh Boyer
2006-11-04  5:16     ` Josh Triplett
2006-11-04  6:09       ` Josh Boyer

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=1162318761.3785.3.camel@zod.rchland.ibm.com \
    --to=jwboyer@jdub.homelinux.org \
    --cc=davej@redhat.com \
    --cc=linux-sparse@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