From: Andreas Ericsson <ae@op5.se>
To: git@vger.kernel.org
Subject: Re: [PATCH] rpmbuild doesn't like '-' in version strings
Date: Sat, 07 Jan 2006 01:04:51 +0100 [thread overview]
Message-ID: <43BF05A3.8060407@op5.se> (raw)
In-Reply-To: <7voe2prniw.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> John Ellson <ellson@research.att.com> writes:
>
>
>>Suggested fix: Use '_' instead of '-'
>
>
> I wonder if the right fix is to change the git-describe output
> before the current output becomes too widespread.
I don't think there's any major risk of the current output being very
widespread. It's not very useful for scripting.
> To really
> fix this problem, I think the rpm target of the main Makefile
> needs to be modified to include something monotonicly increasing
> (e.g. number of seconds since the base commit encoded in base26,
> or something silly like that)
Why not keep it super-simple and just print the number of commits since
whatever tag is found? It only counts commits on the current branch, so
a merge shows up as a single commit. That should more or less be ok
though and goes well with the topic branch model.
> If I cut a binary package out of my
> master and then one of my topic branches, it is very likely they
> will get confused time ordering when they happen to find the
> same base revision.
I suppose this could happen when counting commits as well. People who
build packages from different branches should be shot on sight though,
so I wouldn't worry about it.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2006-01-07 0:04 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 [this message]
2006-01-07 0:47 ` Johannes Schindelin
2006-01-07 1:22 ` Ryan Anderson
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=43BF05A3.8060407@op5.se \
--to=ae@op5.se \
--cc=git@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.