git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFD] making separate-remote layout easier to use
Date: Sat, 25 Nov 2006 15:19:44 -0800	[thread overview]
Message-ID: <7vvel3yuzz.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <ekafpm$fs7$1@sea.gmane.org> (Jakub Narebski's message of "Sat, 25 Nov 2006 23:25:35 +0100")

Jakub Narebski <jnareb@gmail.com> writes:

> Junio C Hamano wrote:
>
>> Now separate-remote layout is the default for newly cloned
>> repositories, I think it is a good time to make further effort
>> to make things easier to use.  Here are some of the ideas off
>> the top of my head.
> [...]
>> * Change the default contents of $GIT_DIR/remotes/origin
>
> The question is: do we continue to use remotes/ file, or do we
> save remotes info in the config file: remote.<name>.url,
> remote.<name>.fetch, remote.<name>.push and branch.<name>.merge
> (in our case '[remote "origin"]' section)?

It is not "the question"; it is irrelevant because
$GIT_DIR/remotes/origin and [remote "origin"] are pretty much
interchangeable, and will hopefully continue to be.

        [remote "origin"]
                url = master.kernel.org:/pub/scm/git/git.git/
                fetch = +refs/heads/master:refs/remotes/origin/master
                fetch = +refs/heads/*:refs/remotes/origin/*

would be the way to express the equilvalent of the example in
the previous message.




  reply	other threads:[~2006-11-25 23:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-25 21:53 [RFD] making separate-remote layout easier to use Junio C Hamano
2006-11-25 22:25 ` Jakub Narebski
2006-11-25 23:19   ` Junio C Hamano [this message]
2006-11-25 23:34     ` Jakub Narebski
2006-11-26  3:37       ` Junio C Hamano
2006-11-26  5:30         ` Junio C Hamano
2006-11-26  3:14     ` Shawn Pearce
2006-11-26  3:48       ` Junio C Hamano
2006-11-26  3:34   ` Shawn Pearce
2006-11-26  3:58     ` Junio C Hamano
2006-11-26  4:23       ` Shawn Pearce
2006-11-26  5:11         ` Junio C Hamano
2006-11-26  7:39           ` Shawn Pearce
2006-11-26  9:13             ` Junio C Hamano
2006-11-26  9:43               ` Jakub Narebski
2006-11-27  0:59       ` Josef Weidendorfer
2006-11-27  1:21         ` Junio C Hamano
2006-11-30 18:16       ` Jon Loeliger
2006-11-30 21:22         ` Junio C Hamano
2006-11-26  9:32     ` Jakub Narebski
2006-11-27  0:41 ` Josef Weidendorfer
2006-11-29 21:32 ` Jon Loeliger

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=7vvel3yuzz.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.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).