From: Marc Branchaud <marcnarc@xiplink.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2012, #09; Thu, 27)
Date: Fri, 28 Sep 2012 09:57:34 -0400 [thread overview]
Message-ID: <5065ACCE.3060302@xiplink.com> (raw)
In-Reply-To: <7v3922om03.fsf@alter.siamese.dyndns.org>
On 12-09-27 11:38 PM, Junio C Hamano wrote:
>
> * mb/remote-default-nn-origin (2012-07-11) 6 commits
> - Teach get_default_remote to respect remote.default.
> - Test that plain "git fetch" uses remote.default when on a detached HEAD.
> - Teach clone to set remote.default.
> - Teach "git remote" about remote.default.
> - Teach remote.c about the remote.default configuration setting.
> - Rename remote.c's default_remote_name static variables.
>
> When the user does not specify what remote to interact with, we
> often attempt to use 'origin'. This can now be customized via a
> configuration variable.
>
> Expecting a reroll.
>
> "The first remote becomes the default" bit is better done as a
> separate step.
Unfortunately my days have been too full to progress this. I'm still
planning to get to it when there's an opportunity. The next iteration
would add the settings required to enable the migration plan that Junio
outlined here:
http://article.gmane.org/gmane.comp.version-control.git/201332
In the meantime, anyone else who feels like taking this up is more than
welcome. The relevant threads are:
http://thread.gmane.org/gmane.comp.version-control.git/200145
http://thread.gmane.org/gmane.comp.version-control.git/201065
http://thread.gmane.org/gmane.comp.version-control.git/201306
M.
next prev parent reply other threads:[~2012-09-28 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 3:38 What's cooking in git.git (Sep 2012, #09; Thu, 27) Junio C Hamano
2012-09-28 13:57 ` Marc Branchaud [this message]
2012-09-28 17:29 ` Junio C Hamano
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=5065ACCE.3060302@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).