From: Scott Kyle <scott@appden.com>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: "Jonathan Nieder" <jrnieder@gmail.com>,
"Kevin Ballard" <kevin@sb.org>,
"Ævar Arnfjörð" <avarab@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] completion: Add PS1 configuration for submodules
Date: Tue, 21 Dec 2010 14:56:22 -0800 [thread overview]
Message-ID: <AANLkTimCjRq=rJ5FA7QRCyp=7B8q5R7AtuVPiTimwVR8@mail.gmail.com> (raw)
In-Reply-To: <4D06621F.6010101@web.de>
On Mon, Dec 13, 2010 at 10:12 AM, Jens Lehmann <Jens.Lehmann@web.de> wrote:
> Am 12.12.2010 07:38, schrieb Jonathan Nieder:
>> Scott Kyle wrote:
>>> On Tue, Dec 7, 2010 at 1:29 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>>>> Scott Kyle wrote:
>>
>>>>> If I set the "submodule.<name>.ignore" then diffing around inside my
>>>>> history will not show the changes to that particular submodule.
>>>>
>>>> Even if you set it to "dirty"?
>>>
>>> Setting it to "dirty" is far less disruptive, you're right, but that
>>> wouldn't do me much good since my submodules are often on different
>>> branches while developing.
>>
>> Ah, I see now. How about something like this? Untested, just a
>> vague sketch to show the idea.
>
> Me thinks your proposal of a new "worktree" option makes sense. Let's
> hear what Scott says ...
>
I mostly really like how 'worktree' can let me focus in on only the
submodules I care about. The drawback is that git status would no
longer list my true status. I know that may sound hypocritical, but I
intended for this patch to only affect my PS1. At the same time, I
would like to see the 'worktree' patch taken, regardless of whether
you guys find mine useful.
next prev parent reply other threads:[~2010-12-21 22:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 23:22 [PATCH] completion: Add PS1 configuration for submodules Scott Kyle
2010-12-07 9:40 ` SZEDER Gábor
2010-12-07 12:15 ` Ævar Arnfjörð Bjarmason
2010-12-07 20:31 ` Kevin Ballard
2010-12-07 21:08 ` Jens Lehmann
2010-12-07 21:17 ` Scott Kyle
2010-12-07 21:28 ` Jens Lehmann
2010-12-07 21:29 ` Jonathan Nieder
2010-12-07 22:59 ` Scott Kyle
2010-12-12 6:38 ` Jonathan Nieder
2010-12-13 18:12 ` Jens Lehmann
2010-12-21 22:56 ` Scott Kyle [this message]
2010-12-07 20:37 ` Scott Kyle
2010-12-07 20:41 ` Kevin Ballard
2010-12-08 0:27 ` Ævar Arnfjörð Bjarmason
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='AANLkTimCjRq=rJ5FA7QRCyp=7B8q5R7AtuVPiTimwVR8@mail.gmail.com' \
--to=scott@appden.com \
--cc=Jens.Lehmann@web.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=kevin@sb.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).