From: Tay Ray Chuan <rctay89@gmail.com>
To: maximilian attems <max@stro.at>
Cc: git@vger.kernel.org
Subject: Re: bug in name-rev on linux-2.6 repo?
Date: Thu, 22 Apr 2010 18:54:18 +0800 [thread overview]
Message-ID: <r2sbe6fef0d1004220354g6443218ezbd0452428ad9e4b5@mail.gmail.com> (raw)
In-Reply-To: <20100421195822.GX10984@baikonur.stro.at>
Hi,
On Thu, Apr 22, 2010 at 3:58 AM, maximilian attems <max@stro.at> wrote:
> ~/src/linux-2.6$ git name-rev a1de02dccf906faba2ee2d99cac56799bda3b96a
> a1de02dccf906faba2ee2d99cac56799bda3b96a undefined
have you fetched tags too?
--
Cheers,
Ray Chuan
next prev parent reply other threads:[~2010-04-22 10:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 19:58 bug in name-rev on linux-2.6 repo? maximilian attems
2010-04-22 10:54 ` Tay Ray Chuan [this message]
2010-04-22 12:14 ` maximilian attems
2010-04-22 12:40 ` Jonathan Nieder
2010-04-22 14:29 ` Andreas Schwab
2010-04-22 14:44 ` Jeff King
2010-04-22 14:54 ` Jeff King
2010-04-22 15:03 ` Jonathan Nieder
2010-04-22 15:17 ` Jeff King
2010-04-22 16:25 ` Jonathan Nieder
2010-04-22 18:20 ` Linus Torvalds
2010-04-24 23:04 ` tytso
2010-04-22 14:51 ` Jonathan Nieder
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=r2sbe6fef0d1004220354g6443218ezbd0452428ad9e4b5@mail.gmail.com \
--to=rctay89@gmail.com \
--cc=git@vger.kernel.org \
--cc=max@stro.at \
/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).