All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: Duy Nguyen <pclouds@gmail.com>,
	"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] pathspec: remove check_path_for_gitlink
Date: Thu, 05 May 2016 23:21:44 -0700	[thread overview]
Message-ID: <xmqq60ur7ll3.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <xmqqpot06oys.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Thu, 05 May 2016 16:54:03 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> When deep/in/ is an unrelated repository, and running either
>
>     git add deep/in/the
>     git add deep/in/the/tree
>
> would add deep/in/the/tree/is-a-leaf.txt to my index, but if I did
>
>     git add deep/in
>
> I'd lose that and suddenly everything there turns into a submodule.

Also, I recall that you floated an idea to declare that

    git add deep/in/the/tree/is-a-leaf.txt

must always behave as if this is done instead:

    git -C deep/in/the/tree/ add is-a-leaf.txt

Even though I am not a huge fan of an operation that crosses module
boundaries, I think that is a sensible semantics of a "cross module
boundary operation" (the actual implementation should not be
iterating over pathspecs and chdir(2)ing around for each and every
one of them, though), if we need "cross module boundary operation"
in order to support end users working on a project with one or more
submodules at the same time.

But treating the bug under discussion as a "feature" will destroy
that future.

  parent reply	other threads:[~2016-05-06  6:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-05 22:31 [PATCH] pathspec: remove check_path_for_gitlink Stefan Beller
2016-05-05 23:09 ` Junio C Hamano
2016-05-05 23:15   ` Stefan Beller
2016-05-05 23:27     ` Junio C Hamano
2016-05-05 23:32       ` Stefan Beller
2016-05-05 23:54         ` Junio C Hamano
2016-05-06  0:28           ` Stefan Beller
2016-05-06  6:21           ` Junio C Hamano [this message]
2016-05-06  6:58             ` Stefan Beller
2016-05-06  7:14               ` Junio C Hamano
2016-05-06 10:30       ` Duy Nguyen
2016-05-06 17:13         ` Stefan Beller
2016-05-06 19:02           ` Junio C Hamano
2016-05-06 19:18             ` Stefan Beller
2016-05-06 20:09               ` Junio C Hamano
2016-05-07  7:16               ` Duy Nguyen

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=xmqq60ur7ll3.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.com \
    --cc=sbeller@google.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.