git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Anderson <ryan@michonline.com>
To: Junio C Hamano <junkio@cox.net>
Cc: John Ellson <ellson@research.att.com>,
	git@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] rpmbuild doesn't like '-' in version strings
Date: Fri, 6 Jan 2006 20:22:21 -0500	[thread overview]
Message-ID: <20060107012221.GA7730@mythryan2.michonline.com> (raw)
In-Reply-To: <7voe2prniw.fsf@assigned-by-dhcp.cox.net>

On Fri, Jan 06, 2006 at 02:37:27PM -0800, Junio C Hamano wrote:
>
> Since I do not understand what that "g"
> stands for anyway, how about doing something like this instead?

I'm pretty sure the "g" is my fault, indirectly.  When I submitted the
"AUTO_LOCALVERSION" patch to Linux, I prepended a -g to it, so it would
be possible to tell versions based off of a git tree apart from versions
based off of a CVS tree that used md5 to make a short, semi-unique
indicator.  Presumably, a CVS variant would've done something like
-c012345678, etc.

So, it's just a little mnemonic to hint that the extra version string
came from a git tree, as opposed to some other semi-random source. It's
value is rather dubious, overall, though.

-- 

Ryan Anderson
  sometimes Pug Majere

  parent reply	other threads:[~2006-01-07  1:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-30 17:29 [PATCH] rpmbuild doesn't like '-' in version strings John Ellson
2006-01-06 22:37 ` Junio C Hamano
2006-01-07  0:04   ` Andreas Ericsson
2006-01-07  0:47     ` Johannes Schindelin
2006-01-07  1:22   ` Ryan Anderson [this message]
2006-01-14 15:39   ` John Ellson
2006-01-14 17:53     ` Linus Torvalds
2006-01-14 19:17     ` Junio C Hamano
2006-01-14 20:25       ` John Ellson
2006-01-14 20:35         ` Junio C Hamano
2006-01-16  9:15         ` Junio C Hamano

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=20060107012221.GA7730@mythryan2.michonline.com \
    --to=ryan@michonline.com \
    --cc=ellson@research.att.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=torvalds@osdl.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).