From: "Lars Hjemli" <hjemli@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: skimo@liacs.nl, "Sven Verdoolaege" <skimo@kotnet.org>,
git@vger.kernel.org, "Eran Tromer" <git2eran@tromer.org>
Subject: Re: [PATCH] unpack-trees.c: assume submodules are clean during check-out
Date: Sat, 4 Aug 2007 13:41:06 +0200 [thread overview]
Message-ID: <8c5c35580708040441ue1c3ef8qc022912a5af4883e@mail.gmail.com> (raw)
In-Reply-To: <7v643vj316.fsf@assigned-by-dhcp.cox.net>
On 8/4/07, Junio C Hamano <gitster@pobox.com> wrote:
> As we explicitly allow
> submodule checkout to drift from the supermodule index entry,
> the check should say "Ok, for submodules, not matching is the
> norm" for now. Later when we have the ability to mark "I care
> about this submodule to be always in sync with the superproject"
> (thereby implementing automatic recursive checkout and perhaps
> diff, among other things), we should check if the submodule in
> question is marked as such and perform the current test.
Yes, this sounds like a sane plan (and a good explanation of the
current semantics: maybe something to include in the release notes for
1.5.3?)
Btw: I've applied your patch to rc-4 and tested the result in my cgit
repo: very nice, and very ack'd ;-)
--
larsh
next prev parent reply other threads:[~2007-08-04 11:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 18:28 [PATCH] unpack-trees.c: assume submodules are clean during check-out Sven Verdoolaege
2007-07-18 7:29 ` Junio C Hamano
2007-08-01 14:05 ` Sven Verdoolaege
2007-08-04 5:13 ` Junio C Hamano
2007-08-04 11:41 ` Lars Hjemli [this message]
2007-08-05 6:02 ` Junio C Hamano
2007-08-05 13:55 ` Sven Verdoolaege
2007-08-04 16:03 ` Eran Tromer
2007-08-05 6:12 ` Junio C Hamano
2007-08-05 14:46 ` Sven Verdoolaege
2007-08-06 18:42 ` Eran Tromer
2007-08-06 19:03 ` Sven Verdoolaege
2007-08-07 3:24 ` Eran Tromer
2007-08-07 8:51 ` Sven Verdoolaege
2007-08-08 1:41 ` Eran Tromer
2007-08-08 11:39 ` Sven Verdoolaege
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=8c5c35580708040441ue1c3ef8qc022912a5af4883e@mail.gmail.com \
--to=hjemli@gmail.com \
--cc=git2eran@tromer.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=skimo@kotnet.org \
--cc=skimo@liacs.nl \
/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).