Re: Documentation (mainly user-manual) patches

From: Shawn O. Pearce <spearce@spearce.org>
Date: May 19, 2007, 04:32 UTC
Message-ID: <20070519043234.GE3141@spearce.org>
In-Reply-To: <20070519041357.GA2679@fieldses.org>

"J. Bruce Fields" <bfields@fieldses.org> wrote:

Show 11 quoted lines

> 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.