list mirror (unofficial, one of many)
 help / color / Atom feed
From: Junio C Hamano <>
To: Jonathan Nieder <>
Cc: Stefan Beller <>,
Subject: Re: [PATCH] FYI / RFC: submodules: introduce repo-like workflow
Date: Fri, 28 Sep 2018 11:08:04 -0700
Message-ID: <> (raw)
In-Reply-To: <>

Jonathan Nieder <> writes:

> (dropping cc-s to my internal address that I don't use on this list
>  and to which bounces)
> Hi,
> Stefan Beller wrote:
>> Internally we have rolled out this as an experiment for
>> "submodules replacing the repo tool[1]". The repo tool is described as:
>>     Repo unifies Git repositories when necessary, performs uploads to the
>>     Gerrit revision control system, and automates parts of the Android
>>     development workflow. Repo is not meant to replace Git, only to make
>>     it easier to work with Git in the context of Android. The repo command
>>     is an executable Python script that you can put anywhere in your path.
> [...]
>> Submodules can also be understood as unifying Git repositories, even more,
>> in the superproject the submodules have relationships between their
>> versions, which the repo tool only provides in releases.
>> The repo tool does not provide these relationships between versions, but
>> all the repositories (in case of Android think of ~1000 git repositories)
>> are put in their place without depending on each other.
>> This comes with a couple of advantages and disadvantages:
> Thanks for describing this background.

Thanks for this.  I probably won't be reading this before other
topics, but I've often found that changes from google were lacking
the backstory to make sense of them as a coherent whole.  

For example, a patch that says "Instead of detaching at the commit
recorded in the superproject, check out the branch with the same
name, even if it points at a different commit.  Here is the write up
of what it does in the Documentation/ and code" is hard to judge
beyond checking if the code does what it claims to do and if the
docs describe what the code does---without backstory like this that
talks about how individual small pieces fit within the plan for the
whole thing, judging if that "what it claims to do" is even sensible
is impossible.

  reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27 22:16 Stefan Beller
2018-09-27 22:27 ` Jonathan Nieder
2018-09-28 18:08   ` Junio C Hamano [this message]
2018-09-28 19:26 ` Ævar Arnfjörð Bjarmason
2018-09-28 20:23   ` Stefan Beller
2019-01-14 22:34 ` Jonathan Nieder

Reply instructions:

You may reply publically 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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link list mirror (unofficial, one of many)

Archives are clonable:
	git clone --mirror
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Newsgroups are available over NNTP:

 note: .onion URLs require Tor:

AGPL code for this site: git clone public-inbox