Re: Branch metainformation

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Apr 20, 2006, 09:37 UTC
Message-ID: <Pine.LNX.4.63.0604201131240.9099@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <e27dqv$u6f$1@sea.gmane.org>

Hi,

On Thu, 20 Apr 2006, Jakub Narebski wrote:

Show 10 quoted lines

> It seems that ever so often there is question posted on this list on which
> the answer is to add '+' in 'pu' branch 'Pull:' line. I think that it is
> not a good policy to have puller to remember which branches can be
> fast-forwarded, and which needs to be merged. It should be an information
> set and stored by person managing the branch (pullee), as some kind of
> metainformation for the branch (like description and optional signature is
> for tags).
> 
> Perhaps then there would be a place for short, one-line description of the
> branch...

I have an alternative in my private repository: When git-pull/git-fetch are called with "-S <nick>", then the current URL is set as URL for that shorthand, and the rest is *added* as Pull line.

However, this all depends on my (rejected) patch to move the remotes information into the config file.

I have not backported the "-S" feature to the non-config remotes, since I 1) do not need it myself, and 2) am wary that it is not that easy to ensure data integrity by shell-scripting.

Ciao, Dscho