git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jens Lehmann <Jens.Lehmann@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Ronald Weiss <weiss.ronald@gmail.com>
Subject: Re: What's cooking in git.git (Apr 2014, #02; Mon, 7)
Date: Tue, 08 Apr 2014 21:20:59 +0200	[thread overview]
Message-ID: <53444C1B.2070603@web.de> (raw)
In-Reply-To: <xmqq38hn4q39.fsf@gitster.dls.corp.google.com>

Am 08.04.2014 20:46, schrieb Junio C Hamano:
> Jens Lehmann <Jens.Lehmann@web.de> writes:
> 
>> Am 08.04.2014 00:19, 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
>>
>> I have two more patches for gitk and git-gui doing the same there,
>> me thinks it would make a lot of sense all four make it into the
>> same version. Should I wait until this topic hits next (or master)
>> or does it make sense to send them to Pat and Paul right away?
> 
> Either would be fine, but I suspect they would appreciate it sooner
> rather than later, if only as an advance notice.

Thanks, will do.

> How do these two relate to and/or interact with what Ronald and you
> have been discussing, by the way?

Only as a prerequisite, as the latter is about making the handling
and overriding of the submodule ignore options consistent for add
and commit. The goal there is to enable users to stage and commit
ignored submodules pretty much like they can do that with ignored
files. And the prerequisite for that is that you'll be able to see
what you staged afterwards.

      reply	other threads:[~2014-04-08 19:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 22:19 What's cooking in git.git (Apr 2014, #02; Mon, 7) Junio C Hamano
2014-04-08 18:35 ` Jens Lehmann
2014-04-08 18:46   ` Junio C Hamano
2014-04-08 19:20     ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53444C1B.2070603@web.de \
    --to=jens.lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=weiss.ronald@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).