From: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Linus Torvalds" <torvalds@osdl.org>,
"Junio C Hamano" <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: [PATCH] Teach the git wrapper about --name-rev and --name-rev-by-tags
Date: Sat, 29 Jul 2006 19:43:29 +0700 [thread overview]
Message-ID: <fcaeb9bf0607290543h12b70c74q54a1fbfc3c8e3b7e@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0607282042470.29667@wbgn013.biozentrum.uni-wuerzburg.de>
On 7/29/06, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> You are probably right. But _I_ want to know that e.g. commit
> a025463bc0ec2c894a88f2dfb44cf88ba71bb712 is really tags/v1.4.0^0~27^2.
> Both are immutable, but the latter is nicer to people than to computers.
I think so too. I had requested a similar feature on the git survey
and was surprised to see this patch. I'd appreciate it.
next prev parent reply other threads:[~2006-07-29 12:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-24 13:10 Slow fetches of tags Ralf Baechle
2006-05-24 16:45 ` Linus Torvalds
2006-05-24 17:21 ` Linus Torvalds
2006-05-24 18:08 ` Junio C Hamano
2006-05-24 19:17 ` Linus Torvalds
2006-05-24 23:43 ` Linus Torvalds
2006-05-25 1:32 ` Junio C Hamano
2006-05-25 4:48 ` Junio C Hamano
2006-05-26 15:42 ` Ralf Baechle
2006-05-27 2:20 ` [PATCH/RFC] upload-pack: stop "ack continue" when we know common commits for wanted refs Junio C Hamano
2006-05-25 13:12 ` Slow fetches of tags Ralf Baechle
2006-07-26 23:27 ` Junio C Hamano
2006-07-28 10:42 ` Johannes Schindelin
2006-07-28 11:12 ` [PATCH] Teach the git wrapper about --name-rev and --name-rev-by-tags Johannes Schindelin
2006-07-28 15:43 ` Junio C Hamano
2006-07-28 16:59 ` Linus Torvalds
2006-07-28 18:53 ` Johannes Schindelin
2006-07-29 12:43 ` Nguyễn Thái Ngọc Duy [this message]
2006-07-29 12:47 ` Johannes Schindelin
2006-05-24 19:06 ` Slow fetches of tags Junio C Hamano
2006-05-24 18:08 ` Ralf Baechle
2006-05-24 18:41 ` Junio C Hamano
2006-05-25 13:27 ` Ralf Baechle
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=fcaeb9bf0607290543h12b70c74q54a1fbfc3c8e3b7e@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.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 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).