git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Jens Lehmann <Jens.Lehmann@web.de>,
	Phil Hord <phil.hord@gmail.com>,
	Junio C Hamano <gitster@pobox.com>,
	Git List <git@vger.kernel.org>
Subject: Re: Composing git repositories
Date: Tue, 2 Apr 2013 12:20:17 -0700	[thread overview]
Message-ID: <20130402192017.GI28148@google.com> (raw)
In-Reply-To: <CALkWK0kCcSgHfmTuQc-0XGHOdm6PPaVHqFeD4bko-zq3pH8mUw@mail.gmail.com>

Ramkumar Ramachandra wrote:
> Jonathan Nieder wrote:

>>         $ git clone git://repo.or.cz/git.git
[...]
>>         Don't forget to "git clone -b todo git://repo.or.cz/git.git git/Meta"
>>         for maintenance scripts.
>>         $
>
> Nope, it's not mandatory for everyone to use dotfiles.git in exactly
> the same way either.  In other words: I'm not sitting in an office and
> working with my colleagues on exactly the same things, in exactly the
> same way; wasn't that the Subversion age?  Some might decide to
> initialize a few submodules, change the URLs of some, and remove some.

Can't a script pointed to in README handle all these things?

>  I'd want my private fork to have commits changing "initialize
> submodule quux" to "don't initialize submodule quux", and be able to
> rebase that on top of upstream.

These would be patches to comment or uncomment repositories in the
list used by your "setup" script.

>                                  Why are you leaning towards solutions
> for very narrow usecases?

I don't think this hostile way of explaining things is warranted. :/

Yours,
Jonathan

  reply	other threads:[~2013-04-02 19:20 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26  7:56 Composing git repositories Ramkumar Ramachandra
2013-03-26 16:39 ` Junio C Hamano
2013-03-27 11:49   ` Ramkumar Ramachandra
2013-03-27 16:06     ` Junio C Hamano
2013-03-27 17:02       ` Ramkumar Ramachandra
2013-03-27 17:16         ` Junio C Hamano
2013-03-27 19:26         ` Jonathan Nieder
2013-03-27 20:18           ` Junio C Hamano
2013-03-27 20:42             ` Jonathan Nieder
2013-03-28 11:48             ` Ramkumar Ramachandra
2013-03-28 20:25               ` Jens Lehmann
2013-03-28 10:01           ` Ramkumar Ramachandra
2013-03-28 18:21             ` Jonathan Nieder
2013-03-28 20:17             ` Jens Lehmann
2013-03-27 23:02         ` Jens Lehmann
2013-03-28  9:16           ` Ramkumar Ramachandra
2013-03-28 20:40             ` Jens Lehmann
2013-03-31 20:34               ` Ramkumar Ramachandra
2013-03-31 22:57                 ` Jonathan Nieder
2013-04-02 17:44                   ` Ramkumar Ramachandra
2013-04-02 17:58                     ` Jeff King
2013-04-02 19:33                       ` Ramkumar Ramachandra
2013-04-02 19:56                     ` Jens Lehmann
2013-04-02 18:03                   ` Junio C Hamano
2013-04-04  6:40                     ` Junio C Hamano
2013-04-05  2:36                       ` Duy Nguyen
2013-04-05  4:53                         ` Junio C Hamano
2013-04-05  5:27                           ` Duy Nguyen
2013-04-05  7:15                             ` Jens Lehmann
2013-03-31 23:50                 ` Phil Hord
2013-04-01 12:14                   ` Jens Lehmann
2013-04-01 14:49                     ` Phil Hord
2013-04-02 18:35                     ` Ramkumar Ramachandra
2013-04-02 18:54                       ` Jonathan Nieder
2013-04-02 19:09                         ` Junio C Hamano
2013-04-02 19:11                         ` Ramkumar Ramachandra
2013-04-02 19:20                           ` Jonathan Nieder [this message]
2013-04-02 19:29                             ` Ramkumar Ramachandra
2013-04-02 19:49                               ` Ramkumar Ramachandra
2013-04-02 19:59                       ` Jens Lehmann
2013-04-01  9:50                 ` Jens Lehmann
2013-04-01  0:16 ` Seth Robertson
2013-04-02 19:19   ` Ramkumar Ramachandra

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=20130402192017.GI28148@google.com \
    --to=jrnieder@gmail.com \
    --cc=Jens.Lehmann@web.de \
    --cc=artagnon@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=phil.hord@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).