From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jens Lehmann <Jens.Lehmann@web.de>,
Johan Herland <johan@herland.net>,
git@vger.kernel.org
Subject: Re: RFC: Making submodules "track" branches
Date: Tue, 8 Jun 2010 23:19:39 +0000 [thread overview]
Message-ID: <AANLkTimApr6P0sQ0FQiNkzhFuftOu1e4VefQxUCXpA53@mail.gmail.com> (raw)
In-Reply-To: <7vbpblruj8.fsf@alter.siamese.dyndns.org>
On Tue, Jun 8, 2010 at 23:09, Junio C Hamano <gitster@pobox.com> wrote:
> Wouldn't it be enough to say --ignore-submodules for your day-to-day work,
> without lying in the gitlink entry in the superproject tree? An entry
> "submodule.foo.branch = fred" in your .gitmodules will still tell your
> local git to update the submodule worktree to work on 'fred' branch. At
> least, an arrangement like that would allow the build infrastructure to
> use --no-ignore-submodules when running its equivalent of GIT-VERSION-GEN
> to notice that what you are building is using something different from
> what the superproject specified to use in the submodule, while not bugging
> you with differences you do not care about (or you already know about and
> are irrelevant to the change you are working on).
Yes I think that's even better, to have no entry in the superproject's
tree at all, and just a repo/branch pair in .gitmodules.
Less confusion and the same features.
next prev parent reply other threads:[~2010-06-08 23:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 23:29 RFC: Making submodules "track" branches Ævar Arnfjörð Bjarmason
2010-06-08 7:12 ` Johan Herland
2010-06-08 15:34 ` Marc Branchaud
2010-06-08 16:09 ` Ævar Arnfjörð Bjarmason
2010-06-08 19:32 ` Marc Branchaud
2010-06-08 20:23 ` Ævar Arnfjörð Bjarmason
2010-06-09 14:36 ` Marc Branchaud
2010-06-08 16:06 ` Jens Lehmann
2010-06-08 21:52 ` Johan Herland
2010-06-09 7:23 ` Jens Lehmann
2010-06-09 8:22 ` Johan Herland
2010-06-09 12:47 ` Steven Michalske
2010-06-09 14:37 ` Johan Herland
2010-06-08 23:09 ` Junio C Hamano
2010-06-08 23:19 ` Ævar Arnfjörð Bjarmason [this message]
2010-06-09 7:09 ` Jens Lehmann
2010-06-09 7:15 ` Jens Lehmann
2010-06-09 15:36 ` Marc Branchaud
2010-06-09 18:54 ` Ævar Arnfjörð Bjarmason
2012-11-20 11:16 ` nottrobin
2012-11-20 12:04 ` W. Trevor King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimApr6P0sQ0FQiNkzhFuftOu1e4VefQxUCXpA53@mail.gmail.com \
--to=avarab@gmail.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johan@herland.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).