git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 22 May 2007 02:17:32 -0400	[thread overview]
Message-ID: <20070522061732.GC11636@spearce.org> (raw)
In-Reply-To: <7vhcq59yiy.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano <junkio@cox.net> wrote:
> "Shawn O. Pearce" <spearce@spearce.org> writes:
> 
> > Teach git-describe how to run name-rev
> 
> Sorry for a belated question, but is there a reason not to do
> this (on top)?

Nope, I just completely missed it.  Please make it so!  ;-)
 
> diff --git a/builtin-describe.c b/builtin-describe.c
> index efbd43f..2a32af6 100644
> --- a/builtin-describe.c
> +++ b/builtin-describe.c
> @@ -283,8 +283,7 @@ int cmd_describe(int argc, const char **argv, const char *prefix)
>  		nr[2] = "--tags";
>  		memcpy(nr + 3, argv + i, (argc - i) * sizeof(char*));
>  		nr[3 + argc - i] = NULL;
> -		execv_git_cmd(nr);
> -		die("unable to start %s", nr[0]);
> +		return cmd_name_rev(3 + argc - i, nr, prefix);
>  	}
>  
>  	if (argc <= i)
> 

-- 
Shawn.

      reply	other threads:[~2007-05-22  6:17 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
2007-05-21  8:01                           ` Matthieu Moy
2007-05-22  6:13                         ` Junio C Hamano
2007-05-22  6:17                           ` Shawn O. Pearce [this message]

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=20070522061732.GC11636@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 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).