Re: [RFC 2/2] Automatically transform .git/{branches,remotes} into .git/config
- From
Petr Baudis <pasky@suse.cz>
- Date
- Nov 27, 2005, 12:59 UTC
- Message-ID
- <20051127125945.GD22159@pasky.or.cz>
- In-Reply-To
- <Pine.LNX.4.63.0511211455120.13775@wbgn013.biozentrum.uni-wuerzburg.de>
Dear diary, on Mon, Nov 21, 2005 at 02:56:41PM CET, I got a letter where Johannes Schindelin <Johannes.Schindelin@gmx.de> said that...
Show 5 quoted lines
> With this patch, git automatically extracts the information from > .git/branches and .git/remotes, puts it into .git/config, and renames the > directories to .git/branches.old and .git/remotes.old, respectively. > > Signed-off-by: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Please don't do so for .git/branches, that is primarily Cogito thing and you will make it impossible to use GIT and Cogito on the same repository - the moment the user uses git-pull on the repository, his Cogito configuration is trashed and he has even no reliable undo mechanism.
And in another thread (we have too many threads for this subject ;-) I've tried to explain that branches and remotes are different concepts, which live in different namespaces and have different semantics, so rewriting branches to remotes is a bad idea anyway.
-- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ VI has two modes: the one in which it beeps and the one in which it doesn't.