Re: [RFH] An early draft of v1.5.0 release notes
- From
Jakub Narebski <jnareb@gmail.com>
- Date
- Dec 28, 2006, 11:50 UTC
- Message-ID
- <en0asv$bjm$1@sea.gmane.org>
- In-Reply-To
- <7v64bw3ewk.fsf@assigned-by-dhcp.cox.net>
[Cc: git@vger.kernel.org, Junio C Hamano <junkio@cox.net>, "Horst H. von Brand" <vonbrand@inf.utfsm.cl>]
Junio C Hamano wrote:
Show 15 quoted lines
> "Horst H. von Brand" <vonbrand@inf.utfsm.cl> writes: > >> Junio C Hamano <junkio@cox.net> wrote: >>> This is still rough, but I think we have a pretty good idea what >>> will and what won't be in v1.5.0 by now, and end-of-year is a >>> good slow time to summarize what we have done. >> >> Could somebody please summarize how to "upgrade" a repository to the new >> layout? This has got my head spinning... and I'm /not/ cloning the >> various repos I've got here just to take advantage of the changes. > > The old layout was to map remote branch $B to local tracking > branch .git/refs/heads/$B, unless $B == 'master' in which case > it was mapped to .git/refs/heads/origin (and I think we > discarded 'origin' at remote).
How to discard 'origin' in the new wildcard / globbing remote config? IIRC there was proposal to use '-' or '!' to exclude branch from fetching, but no code...
[...]
> - create the config section like the above in .git/config, and
You can use contrib/remotes2config.sh script...
> - remove .git/remotes/origin when you are done.
...which saves remotes/ under remotes.old/
-- Jakub Narebski Warsaw, Poland ShadeHawk on #git