Git development
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/3] diff options: Introduce --ignore-submodules
Date: Thu, 15 May 2008 02:09:22 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.1.00.0805150204440.30431@racer> (raw)
In-Reply-To: <7vod78k022.fsf@gitster.siamese.dyndns.org>

Hi,

On Wed, 14 May 2008, Junio C Hamano wrote:

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > On Wed, 14 May 2008, Junio C Hamano wrote:
> >
> >> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> >> 
> >> > The point is: for the sake of a script (which wants to ignore 
> >> > submodules) asking if there is a diff, I think it makes sense to 
> >> > not ignore those changes.  IOW I think my patch is enough for the 
> >> > purpose of getting stash/rebase to behave.
> >> 
> >> But the patch is not about stash/rebase but affects all diff users, 
> >> doesn't it?
> >
> > Does it?  I thought I hid all that special handling behind the 
> > --ignore-submodules options.
> 
> That's exactly the point.  The option reads "ignore submodules", not 
> "special option for use only by stash and rebase".

But it also does not read "ignore submodules and those blobs/trees that 
happen to replace (or be replaced by) submodules".

I think it is not a bad thing to call it "ignore submodules", but show the 
submodules when something else than a submodule is involved, too.

I see where you are heading with the "split diff into removal of submodule 
/ addition of a blob", but I think that would be overly clever, and not 
helpful.  I know that I would want to have that marked as a problem when 
rebasing.

Ciao,
Dscho

  reply	other threads:[~2008-05-15  1:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 17:03 [PATCH 0/3] sane rebase/stash support with submodules Johannes Schindelin
2008-05-14 17:03 ` [PATCH 1/3] diff options: Introduce --ignore-submodules Johannes Schindelin
2008-05-14 18:28   ` Junio C Hamano
2008-05-14 18:42     ` Johannes Schindelin
2008-05-14 19:17       ` Junio C Hamano
2008-05-14 22:09         ` Johannes Schindelin
2008-05-14 22:12           ` Junio C Hamano
2008-05-15  1:09             ` Johannes Schindelin [this message]
2008-05-15  1:50               ` Junio C Hamano
2008-05-15 13:58                 ` Johannes Schindelin
2008-05-14 17:03 ` [PATCH 2/3] Teach update-index about --ignore-submodules Johannes Schindelin
2008-05-14 17:03 ` [PATCH 3/3] Ignore dirty submodule states during rebase and stash Johannes Schindelin

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=alpine.DEB.1.00.0805150204440.30431@racer \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox