From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Brian Gernhardt <benji@silverinsanity.com>,
Anand Kumria <wildfire@progsoc.org>,
git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH] Cross-reference the manpages for git-name-rev and git-describe
Date: Mon, 21 May 2007 03:54:13 -0400 [thread overview]
Message-ID: <20070521075413.GQ3141@spearce.org> (raw)
In-Reply-To: <7viramfwkq.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> > Junio C Hamano <junkio@cox.net> wrote:
> >> wouldn't this be useful?
> >>
> >> $ git-describe --contains --tags 1b600e659
> >> v1.5.0-rc3~34
>
> Now we need to make sure that the name of the option --contains
> is sane, I guess.
I think its sane. I wanted to do a --contains option to describe
a while back, for this reason, but just didn't get around to it.
You also suggested it. Looks like at least two people came up with
that option independently. That's not too bad.
Feel free to edit the patch if something else better comes up.
--
Shawn.
next prev parent reply other threads:[~2007-05-21 7:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 10:30 Commits gone AWOL, but not reported by git-fsck --unreachable Robin H. Johnson
2007-05-19 11:52 ` Jeff King
2007-05-19 12:09 ` Robin H. Johnson
2007-05-19 12:11 ` Jeff King
2007-05-19 15:45 ` Anand Kumria
2007-05-19 16:08 ` Matthieu Moy
2007-05-19 16:20 ` Brian Gernhardt
2007-05-19 16:55 ` Matthieu Moy
2007-05-19 17:13 ` Brian Gernhardt
2007-05-19 18:15 ` Junio C Hamano
2007-05-20 12:37 ` [PATCH] Cross-reference the manpages for git-name-rev and git-describe (was Re: Commits gone AWOL, but not reported by git-fsck --unreachable) Matthieu Moy
[not found] ` <7vsl9rmkm0.fsf@assigned-by-dhcp.cox.net>
2007-05-21 7:20 ` [PATCH] Cross-reference the manpages for git-name-rev and git-describe Shawn O. Pearce
2007-05-21 7:46 ` Junio C Hamano
2007-05-21 7:54 ` Shawn O. Pearce [this message]
2007-05-21 8:01 ` Matthieu Moy
2007-05-22 6:13 ` Junio C Hamano
2007-05-22 6:17 ` Shawn O. Pearce
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=20070521075413.GQ3141@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=benji@silverinsanity.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=wildfire@progsoc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.