From: Junio C Hamano <gitster@pobox•com>
To: Stefan Beller <sbeller@google•com>
Cc: jrnieder@gmail•com, git@vger•kernel.org
Subject: Re: [RFD/PATCH] submodule doc: describe where we can configure them
Date: Wed, 04 May 2016 13:48:50 -0700 [thread overview]
Message-ID: <xmqqh9edft1p.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1462317985-640-1-git-send-email-sbeller@google.com> (Stefan Beller's message of "Tue, 3 May 2016 16:26:25 -0700")
Stefan Beller <sbeller@google•com> writes:
> This is similar to the gitignore document, but doesn't mirror
> the current situation. It is rather meant to start a discussion for
> the right approach for mirroring repositories with submodules.
>
> Signed-off-by: Stefan Beller <sbeller@google•com>
> ---
>
> Jonathan, is this something you had in mind?
>
> Documentation/git-submodule.txt | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/Documentation/git-submodule.txt b/Documentation/git-submodule.txt
> index 13adebf..b5559e5 100644
> --- a/Documentation/git-submodule.txt
> +++ b/Documentation/git-submodule.txt
> @@ -59,6 +59,22 @@ instead of treating the other project as a submodule. Directories
> that come from both projects can be cloned and checked out as a whole
> if you choose to go that route.
>
> +Submodule operations can be configured using the following mechanisms
> +(from highest to lowest precedence):
> +
> + * the command line for those commands that support taking submodule specs.
Sorry, but have we introduced <submodule spec> as a Git lingo? What
does it mean?
> +
> + * the configuration file `$GIT_DIR/config`.
> +
> + * the configuration file `config` found in the `refs/submodule/config` branch.
> + This can be used to overwrite the upstream configuration in the `.gitmodules`
> + file without changing the history of the project.
> + Useful options here are overwriting the base, where relative URLs apply to,
> + when mirroring only parts of the larger collection of submodules.
This smells like something server side people may come up with; how
would an end user with a usual "repository with working tree" layout
futz with this thing? Can it even be checked out, or would we have
a UI similar to "notes"?
> + * the `.gitmodules` file inside the repository. A project usually includes this
> + file to suggest defaults for the upstream collection of repositories.
> +
> COMMANDS
> --------
> add::
prev parent reply other threads:[~2016-05-04 20:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 23:26 [RFD/PATCH] submodule doc: describe where we can configure them Stefan Beller
2016-05-03 23:56 ` Jonathan Nieder
2016-05-04 0:59 ` Stefan Beller
2016-05-04 15:01 ` Heiko Voigt
2016-05-04 20:50 ` Stefan Beller
2016-05-08 21:54 ` Heiko Voigt
2016-05-09 17:32 ` Stefan Beller
2016-05-11 16:54 ` Heiko Voigt
2016-05-04 21:13 ` Junio C Hamano
2016-05-08 22:01 ` Heiko Voigt
2016-05-09 16:19 ` Junio C Hamano
2016-05-11 15:50 ` Heiko Voigt
2016-05-04 20:48 ` Junio C Hamano [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=xmqqh9edft1p.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jrnieder@gmail$(echo .)com \
--cc=sbeller@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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