git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [RFC 2/2] Automatically transform .git/{branches,remotes} into .git/config
Date: Sun, 27 Nov 2005 13:59:45 +0100	[thread overview]
Message-ID: <20051127125945.GD22159@pasky.or.cz> (raw)
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...
> 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.

  parent reply	other threads:[~2005-11-27 12:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 13:56 [RFC 2/2] Automatically transform .git/{branches,remotes} into .git/config Johannes Schindelin
2005-11-21 15:44 ` Josef Weidendorfer
2005-11-21 15:57   ` Johannes Schindelin
2005-11-21 16:25     ` Josef Weidendorfer
2005-11-21 16:34     ` Andreas Ericsson
2005-11-21 22:26     ` Junio C Hamano
2005-11-27 12:59 ` Petr Baudis [this message]
2005-11-28  1:52   ` Johannes Schindelin
2005-11-28  6:22     ` Junio C Hamano
2005-11-28  8:43       ` Andreas Ericsson
2005-11-28  9:14         ` Junio C Hamano
2005-11-28 12:59         ` Josef Weidendorfer
2005-11-28 13:11           ` Andreas Ericsson
2005-11-28 14:32             ` Generic configuration plumbing (Was: Re: [RFC 2/2] Automatically transform...) Josef Weidendorfer
2005-11-28 15:26               ` Johannes Schindelin
2005-11-28 13:48           ` [RFC 2/2] Automatically transform .git/{branches,remotes} into .git/config Petr Baudis
2005-11-28 15:03             ` Josef Weidendorfer
2005-11-29  6:04           ` Junio C Hamano
2005-11-28 16:29       ` Johannes Schindelin
2005-11-28 13:59     ` Petr Baudis
2005-11-28 16:33       ` Johannes Schindelin

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=20051127125945.GD22159@pasky.or.cz \
    --to=pasky@suse.cz \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    /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).