From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [CFH] Remotes conversion script
Date: Mon, 25 Sep 2006 01:40:26 +0200 [thread overview]
Message-ID: <ef750s$jg4$1@sea.gmane.org> (raw)
In-Reply-To: 20060924231108.GE20017@pasky.or.cz
Petr Baudis wrote:
> Dear diary, on Mon, Sep 25, 2006 at 01:04:41AM CEST, I got a letter
> where Jakub Narebski <jnareb@gmail.com> said that...
>> Petr Baudis wrote:
>>
>> > Dear diary, on Mon, Sep 25, 2006 at 12:34:24AM CEST, I got a letter
>> > where Santi <sbejar@gmail.com> said that...
>> >> It could be I'm wrong (for sure, I miss something), but I see the
>> >> branches/ files like [remote] sections files with just one fetch:
>> >>
>> >> .git/branches/git:
>> >> git://...../git.gi
>> >>
>> >> would be:
>> >>
>> >> [remote "git"]
>> >> url=git://...../git.git
>> >> fetch=refs/heads/master:refs/heads/git
>> >
>> > That's basically right, the point is that with moving to remotes
>> > support, we will make each remote live in its own separate namespace,
>>
>> Which is overkill if we fetch only from one directory.
>
> Why?
s/directory/repository/ of course. And as of why: I'd rather have 'next',
'maint, 'html', 'man' in main namespace (with 'origin' substituting
'master') instead of remotes/origin/next etc.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-09-24 23:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 21:21 [CFH] Remotes conversion script Petr Baudis
2006-09-24 21:39 ` Jakub Narebski
2006-09-24 21:49 ` Johannes Schindelin
2006-09-24 22:57 ` Jakub Narebski
2006-09-24 23:06 ` Jakub Narebski
2006-09-24 23:18 ` Santi
2006-09-24 21:46 ` Johannes Schindelin
[not found] ` <8aa486160609241457u40fffdd8h298e44351749bb29@mail.gmail.com>
2006-09-24 22:16 ` Petr Baudis
2006-09-24 22:34 ` Santi
2006-09-24 22:40 ` Petr Baudis
2006-09-24 23:04 ` Jakub Narebski
2006-09-24 23:11 ` Petr Baudis
2006-09-24 23:40 ` Jakub Narebski [this message]
2006-09-24 23:50 ` Petr Baudis
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='ef750s$jg4$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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).