From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Toralf Förster" <toralf.foerster@gmx.de>, git@vger.kernel.org
Subject: Re: feature request: git-log should accept sth like v2.6.26-rc8-227
Date: Thu, 10 Jul 2008 12:42:53 -0700 (PDT) [thread overview]
Message-ID: <m3d4lledbn.fsf@localhost.localdomain> (raw)
In-Reply-To: <7vk5ftpnek.fsf@gitster.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> Toralf Förster <toralf.foerster@gmx.de> writes:
>
> > git-describe gives an informative string about the current status:
> > tfoerste@n22 ~/devel/linux-2.6 $ git describe
> > v2.6.26-rc9-56-g6329d30
> >
> > I appended those strings to the names of my UML kernel executables.
> > Unfortunately I didn't used the commit id and now I'm wondering whether git
> > could accept v2.6.26-rc9-56 as well in future.
>
> It does take v2.6.26-rc9-56-g6329d30.
>
> It will never take v2.6.26-rc9-56. The world is not linear.
Nevertheless it _could_ be unique.
Besides, it would be nice to have some command (git-rev-parse perhaps?)
which could take ambiguous commit-ish, and list all commit which matches
it.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-07-10 19:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 18:57 feature request: git-log should accept sth like v2.6.26-rc8-227 Toralf Förster
2008-07-10 19:08 ` Junio C Hamano
2008-07-10 19:42 ` Jakub Narebski [this message]
2008-07-10 19:52 ` Toralf Förster
2008-07-10 20:03 ` Junio C Hamano
2008-07-10 22:24 ` Johannes Schindelin
2008-07-10 22:52 ` Junio C Hamano
2008-07-10 23:08 ` Jakub Narebski
2008-07-10 23:47 ` Johannes Schindelin
2008-07-10 20:36 ` Linus Torvalds
2008-07-10 19:29 ` Johannes Schindelin
2008-07-11 13:39 ` Toralf Förster
2008-07-11 14:36 ` Johannes Schindelin
2008-07-11 14:44 ` Toralf Förster
2008-07-11 14:44 ` Dmitry Potapov
2008-07-11 14:58 ` Toralf Förster
2008-07-11 19:29 ` Dmitry Potapov
2008-07-11 19:57 ` Johannes Schindelin
2008-07-11 20:35 ` Johannes Schindelin
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=m3d4lledbn.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=toralf.foerster@gmx.de \
/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).