From: Jens Lehmann <Jens.Lehmann@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Johan Herland <johan@herland.net>
Subject: Re: What's cooking in git.git (Jun 2014, #01; Tue, 3)
Date: Wed, 04 Jun 2014 23:00:30 +0200 [thread overview]
Message-ID: <538F88EE.5070102@web.de> (raw)
In-Reply-To: <xmqqwqcwtn5u.fsf@gitster.dls.corp.google.com>
Am 04.06.2014 22:50, schrieb Junio C Hamano:
> Jens Lehmann <Jens.Lehmann@web.de> writes:
>
>> Am 04.06.2014 00:16, schrieb Junio C Hamano:
>>> * jl/status-added-submodule-is-never-ignored (2014-04-07) 2 commits
>>> - commit -m: commit staged submodules regardless of ignore config
>>> - status/commit: show staged submodules regardless of ignore config
>>>
>>> There also are a few patches Ronald Weiss and Jens are working on
>>> polishing around this topic, and a patch from Jens each for gitk
>>> and git-gui.
>>>
>>> Waiting for the dust to settle until picking them up all.
>>
>> To me it looks like the dust settled enough around that part of the
>> topic and I remember consensus about that change. But it would be
>> nice to have the gitk and git-gui patches in at the same time.
>
> Yes, what I meant was that after the dust settled, it may turn out
> that these two may need to be adjusted. If these two commits can be
> used without any change as a base for any further development, that
> is good---shall I move it back to "Cooking" category?
I'm not aware of any necessary adjustments, so I'd appreciate if
they'd be moved back into "Cooking".
prev parent reply other threads:[~2014-06-04 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 22:16 What's cooking in git.git (Jun 2014, #01; Tue, 3) Junio C Hamano
2014-06-03 23:52 ` Richard Hansen
2014-06-04 19:15 ` Jens Lehmann
2014-06-04 20:50 ` Junio C Hamano
2014-06-04 21:00 ` 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=538F88EE.5070102@web.de \
--to=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.
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).