From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: t5515 in general
Date: Sun, 17 Jun 2007 01:04:37 -0700 [thread overview]
Message-ID: <7v4pl70zxm.fsf@assigned-by-dhcp.pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706170034540.4740@iabervon.org> (Daniel Barkalow's message of "Sun, 17 Jun 2007 02:06:51 -0400 (EDT)")
In general I would agree that the whole "backward compatible"
thing we do with .git/branches and then .git/remotes when we
really went to the new model of using .git/config primarily was
done too cautiously, in that the configuration would not affect
existing setup that used branches and remotes, as they did not
have any way to express those new concepts (i.e. per branch
default remote, and per branch default merge sources).
I am actually in favor of killing .git/branches support way
before we do 1.6.0, and .git/remotes by the time we do 1.6.0.
But if you can arrange the url/fetch configurations to be still
taken from these old locations while applying per-branch default
remote and merge from .git/config, that would probably be easier
for people to migrate to .git/config only style.
prev parent reply other threads:[~2007-06-17 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 6:06 t5515 in general Daniel Barkalow
2007-06-17 8:04 ` Junio C Hamano [this message]
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=7v4pl70zxm.fsf@assigned-by-dhcp.pobox.com \
--to=gitster@pobox.com \
--cc=barkalow@iabervon.org \
--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