From: Junio C Hamano <gitster@pobox.com>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2013, #03; Wed, 6)
Date: Wed, 06 Feb 2013 11:39:29 -0800 [thread overview]
Message-ID: <7vsj59b5am.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <5112AE34.6080107@web.de> (Jens Lehmann's message of "Wed, 06 Feb 2013 20:25:40 +0100")
Jens Lehmann <Jens.Lehmann@web.de> writes:
> Am 06.02.2013 19:29, schrieb Junio C Hamano:
>> * jl/submodule-deinit (2013-02-04) 1 commit
>> - submodule: add 'deinit' command
>>
>> There was no Porcelain way to say "I no longer am interested in
>> this submodule", once you express your interest in a submodule with
>> "submodule init". "submodule deinit" is the way to do so.
>>
>> Will merge to 'next'.
>
> Oops, I though you were waiting for a reroll. Currently I'm having the
> appended interdiff compared to your version. Changes are:
>
> - Add deinit to the --force documentation of "git submodule"
> - Never remove submodules containing a .git dir, even when forced
> - diagnostic output when "rm -rf" or "mkdir" fails
> - More test cases
>
> And I wanted to add three more test cases for modified submodules before
> sending v4. You could squash in the first two hunks into the commit you
> have in pu and I'll send a follow up patch with the extra tests soon or
> you could wait for me sending an updated patch. What do you think?
I haven't merged it down to 'next' yet. So please proceed as you
planned. Thanks for stopping me.
prev parent reply other threads:[~2013-02-06 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 18:29 What's cooking in git.git (Feb 2013, #03; Wed, 6) Junio C Hamano
2013-02-06 19:25 ` Jens Lehmann
2013-02-06 19:39 ` 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=7vsj59b5am.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
/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).