From: Andy Parkins <andyparkins@gmail•com>
To: git@vger•kernel.org
Cc: Junio C Hamano <junkio@cox•net>
Subject: Re: [PATCH 0/8] git-repack --max-pack-size
Date: Tue, 1 May 2007 09:26:33 +0100 [thread overview]
Message-ID: <200705010926.35265.andyparkins@gmail.com> (raw)
In-Reply-To: <7v7irt9qm1.fsf@assigned-by-dhcp.cox.net>
On Tuesday 2007 May 01, Junio C Hamano wrote:
> Which leaves 'master' right now at v1.5.2-rc1 while 'next' at
> v1.5.2-rc1-687-gcb3892c; we might want to do something about
> this apparent discrepancy.
It's perfect - I'd say that it's exactly right.
git-describe is for making unique - human readable names for points in
history, not for describing the tree. It makes no difference that A and B
have the same tree, they are different points.
I've always thought of git-describe as being a way of mapping a commit hash to
a nicer looking name. If A and B are different commits then they should have
different names.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail•com
next prev parent reply other threads:[~2007-05-01 8:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 23:16 [PATCH 0/8] git-repack --max-pack-size Dana How
2007-05-01 3:20 ` Junio C Hamano
2007-05-01 4:37 ` Shawn O. Pearce
2007-05-01 8:26 ` Andy Parkins [this message]
2007-05-01 9:10 ` Junio C Hamano
2007-05-01 9:36 ` Andy Parkins
2007-05-01 14:46 ` Nicolas Pitre
2007-05-01 17:11 ` Junio C Hamano
2007-05-01 17:17 ` Nicolas Pitre
2007-05-01 17:42 ` Johannes Schindelin
2007-05-01 19:07 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2007-04-08 23:17 Dana How
2007-04-09 2:33 ` Nicolas Pitre
2007-04-09 18:54 ` Dana How
2007-04-09 19:43 ` Dana How
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=200705010926.35265.andyparkins@gmail.com \
--to=andyparkins@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=junkio@cox$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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