From: Jens Lehmann <Jens.Lehmann@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "Michał Górny" <mgorny@gentoo.org>,
"Phil Hord" <phil.hord@gmail.com>,
"Heiko Voigt" <hvoigt@hvoigt.net>
Subject: Re: [PATCH v3] Teach rm to remove submodules unless they contain a git directory
Date: Wed, 12 Sep 2012 21:24:17 +0200 [thread overview]
Message-ID: <5050E161.9080203@web.de> (raw)
In-Reply-To: <7vhar4gxdq.fsf@alter.siamese.dyndns.org>
Am 11.09.2012 21:41, schrieb Junio C Hamano:
> Lilewise. It may make sense to introduce a helper function to tell
> if it is a submodule on our side by checking only the stage #2 entry
> when you see a nagetive pos returned from cache_name_pos() and call
> it "is_ours_submodule?()" or something.
Thanks, will do so.
prev parent reply other threads:[~2012-09-12 19:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 23:55 What's cooking in git.git (Sep 2012, #03; Mon, 10) Junio C Hamano
2012-09-11 18:34 ` [PATCH v3] Teach rm to remove submodules unless they contain a git directory Jens Lehmann
2012-09-11 19:41 ` Junio C Hamano
2012-09-12 19:21 ` Suggestions for "What's cooking" Jens Lehmann
2012-09-12 19:37 ` Jeff King
2012-09-12 20:08 ` Dan Johnson
2012-09-12 21:49 ` Junio C Hamano
2012-09-12 22:49 ` Philip Oakley
2012-09-13 5:14 ` Andrew Ardill
2012-09-13 18:06 ` Junio C Hamano
2012-09-14 2:11 ` Andrew Ardill
2012-09-14 2:29 ` Junio C Hamano
2012-09-14 3:58 ` Andrew Ardill
2012-09-14 4:24 ` Junio C Hamano
2012-09-14 6:00 ` Philip Oakley
2012-09-13 7:09 ` Michael Haggerty
2012-09-13 7:21 ` Philip Oakley
2012-09-13 15:09 ` Junio C Hamano
2012-09-14 4:47 ` Junio C Hamano
2012-09-14 7:26 ` Michael Haggerty
2012-09-14 20:20 ` Philip Oakley
2012-09-12 19:24 ` 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=5050E161.9080203@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hvoigt@hvoigt.net \
--cc=mgorny@gentoo.org \
--cc=phil.hord@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.