git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Petr Baudis <pasky@suse.cz>, Junio C Hamano <junkio@cox.net>,
	git@vger.kernel.org
Subject: Re: Documentation (mainly user-manual) patches
Date: Sat, 19 May 2007 00:32:34 -0400	[thread overview]
Message-ID: <20070519043234.GE3141@spearce.org> (raw)
In-Reply-To: <20070519041357.GA2679@fieldses.org>

"J. Bruce Fields" <bfields@fieldses.org> wrote:
> But, actually, I tried it just now and it only gave the url:
> 
> 	The following changes since commit 164b19893ab5bc66b531a26480149a0dff082969:
> 	  Michael Hendricks (1):
> 		Document core.excludesfile for git-add
> 
> 	are found in the git repository at:
> 
> 		git://linux-nfs.org/~bfields/git.git
> 
> How's it supposed to figure out the branch name?

It connects to the remote URL, lists the refs found there, and
finds any that has the commit you passed in as the 3rd argument
(defaults to HEAD).  If none match it prints ..BRANCH.NOT.VERIFIED..
as the branch name, to signal no branch points at the given commit,
which means it cannot be (easily) pulled.

Not getting that means you have too old of a Git to have my branch
improvements.  It was in ff06c743dc, which is in master and hence
should be in 1.5.2 final.

> (And I'm not sure
> about that "change since commit..." stuff--that seems like slight
> overkill.)

Yea, it can be a little overkill sometimes.  But the maintainer
knows where you started from.  If that commit is horribly old he
might wonder what is going on.  ;-)

-- 
Shawn.

  reply	other threads:[~2007-05-19  4:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18  3:37 Documentation (mainly user-manual) patches J. Bruce Fields
2007-05-18  3:39 ` [PATCH] user-manual: reorganize public git repo discussion J. Bruce Fields
2007-05-18  4:56 ` Documentation (mainly user-manual) patches Petr Baudis
2007-05-18 13:43   ` J. Bruce Fields
2007-05-19  4:02     ` Shawn O. Pearce
2007-05-19  4:13       ` J. Bruce Fields
2007-05-19  4:32         ` Shawn O. Pearce [this message]
2007-05-19  5:19           ` J. Bruce Fields

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=20070519043234.GE3141@spearce.org \
    --to=spearce@spearce.org \
    --cc=bfields@fieldses.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=pasky@suse.cz \
    /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).