From: "Dmitry Potapov" <dpotapov@gmail.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: feature request: git-log should accept sth like v2.6.26-rc8-227
Date: Fri, 11 Jul 2008 18:44:23 +0400 [thread overview]
Message-ID: <37fcd2780807110744k3b2a332csdf788dabd172622c@mail.gmail.com> (raw)
In-Reply-To: <200807111539.06606.toralf.foerster@gmx.de>
On Fri, Jul 11, 2008 at 5:39 PM, Toralf Förster <toralf.foerster@gmx.de> wrote:
>
> Ok, following the thread I understand why this feature isn't wanted by all. But
> for the given example (where I only pulled from another git tree) this could
> work, isn't it : ?
>
> tfoerste@n22 ~/devel/linux-2.6 $ git-log v2.6.26-rc9.. | perl -e '@c = grep { /^commit/ } <>; print map { $#c - $i++ . "\t" . $_ } @c'
No, it does not. Running your script, I have
...
56 commit 803a9067e19714ea7b7da760fe92f0d53bfa6994
...
Now, let's see what git-describe thinks about it
$ git describe 803a9067e19714ea7b7da760fe92f0d53bfa6994
v2.6.26-rc9-38-g803a906
Your script is obviously incorrect. It is written in the assumption that
history is linear, but it is not. Even if you pull only from one repo,
this repo still contains *many* branches. Along any branch, you may have
the same number.
Dmitry
next prev parent reply other threads:[~2008-07-11 14:45 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
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 [this message]
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=37fcd2780807110744k3b2a332csdf788dabd172622c@mail.gmail.com \
--to=dpotapov@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--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).