From: Jens Lehmann <Jens.Lehmann@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Sergio Callegari <sergio.callegari@gmail.com>
Subject: Re: [PATCH] git status: ignoring untracked files must apply to submodules too
Date: Sun, 14 Mar 2010 01:55:35 +0100 [thread overview]
Message-ID: <4B9C3407.9090502@web.de> (raw)
In-Reply-To: <7vaaubzrxq.fsf@alter.siamese.dyndns.org>
Am 14.03.2010 01:07, schrieb Junio C Hamano:
> Jens Lehmann <Jens.Lehmann@web.de> writes:
>
>> First: When called from "git status" run_diff_files() calls
>> wt_status_collect_changed_cb() for every file it considers changed, so
>
> This reminds me of another thing, perhaps independent, perhaps related.
> Why aren't we collecting the submodule status in wt_status_collect() to
> begin with? It examines the submodule status in wt_status_print(), but
> that feels quite against the way how the whole "struct wt_status" was
> designed to be used in the first place, I think. Would restuctuing the
> code that way make this easier to handle?
I'm not sure I understand that, but AFAICS in wt_status_print_changed()
only the fact that at least one submodule is dirty is examined to be
able to print the extra hint line. The status of each submodule is
collected in wt_status_collect_changed_cb(), no?
And while not having being active when "struct wt_status" has been
designed, i think adding submodules to the "change" list when they
are dirty makes kind a sense ... but i might be wrong ;-)
prev parent reply other threads:[~2010-03-14 0:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-13 22:00 [PATCH] git status: ignoring untracked files must apply to submodules too Jens Lehmann
2010-03-13 22:24 ` Junio C Hamano
2010-03-13 23:08 ` Jens Lehmann
2010-03-14 0:07 ` Junio C Hamano
2010-03-14 0:55 ` Jens Lehmann [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=4B9C3407.9090502@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sergio.callegari@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).