From: Petr Baudis <pasky@suse.cz>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [CFH] Remotes conversion script
Date: Mon, 25 Sep 2006 01:50:53 +0200 [thread overview]
Message-ID: <20060924235053.GF20017@pasky.or.cz> (raw)
In-Reply-To: <ef750s$jg4$1@sea.gmane.org>
Dear diary, on Mon, Sep 25, 2006 at 01:40:26AM CEST, I got a letter
where Jakub Narebski <jnareb@gmail.com> said that...
> 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.
Well, I don't know. Cogito should stay simple (and stupid) and if you
introduce too much choice, you will lose that. Especially if the choice
is in something already so confusing as branching. And for larger
repositories or more complex distributed branching situations, the
separated-remotes model is clearly superior, so I'd rather keep it for
the simpler cases as well, since if it introduces any hassle, I believe
it's only very minor (and pays off in the long run for the simpler
setups as well, I believe).
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
prev parent reply other threads:[~2006-09-24 23:51 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
2006-09-24 23:50 ` Petr Baudis [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=20060924235053.GF20017@pasky.or.cz \
--to=pasky@suse.cz \
--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).