From: Dave Jones <davej@redhat.com>
To: Josh Boyer <jwboyer@jdub.homelinux.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Official releases?
Date: Tue, 31 Oct 2006 12:08:24 -0500 [thread overview]
Message-ID: <20061031170824.GC23354@redhat.com> (raw)
In-Reply-To: <1162307025.11613.1.camel@zod.rchland.ibm.com>
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.
It's not as 'pretty' as a real version number, but it works with
minimal effort on behalf of Linus.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-10-31 17:57 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 [this message]
2006-10-31 18:19 ` Josh Boyer
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=20061031170824.GC23354@redhat.com \
--to=davej@redhat.com \
--cc=jwboyer@jdub.homelinux.org \
--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