From: Junio C Hamano <gitster@pobox•com>
To: Piotr Krukowiecki <piotr.krukowiecki@gmail•com>
Cc: "Duy Nguyen" <pclouds@gmail•com>,
"Christian Couder" <christian.couder@gmail•com>,
"Matthieu Moy" <Matthieu.Moy@grenoble-inp•fr>,
"Toralf Förster" <toralf.foerster@gmx•de>,
"git@vger•kernel.org" <git@vger•kernel.org>
Subject: Re: RFC: git bisect should accept "paths-to-be-excluded"
Date: Tue, 17 Sep 2013 13:47:07 -0700 [thread overview]
Message-ID: <xmqqwqmfw4z8.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAA01Csp6tjKJ9LqX+9qcJL4t3kfFJCagjZQ=QwddvscPori9Ow@mail.gmail.com> (Piotr Krukowiecki's message of "Tue, 17 Sep 2013 21:41:50 +0200")
Piotr Krukowiecki <piotr.krukowiecki@gmail•com> writes:
> Ignoring (possible) inconsistency thing, I think they are easy to
> understand and use.
Probably you are right (in the sense that I do not offhand think of
a confusing and ambiguous set of positive and negative pathspecs;
others may find holes in my/our thinking).
I am not sure if it will fit well to the current "struct pathspec"
design, though. We could start from "when there is any negative
pathspec, disable the 'optimize away the common leading prefix'
thing", I guess.
next prev parent reply other threads:[~2013-09-17 20:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 12:39 RFC: git bisect should accept "paths-to-be-excluded" Toralf Förster
2013-09-17 7:26 ` Christian Couder
2013-09-17 8:21 ` Matthieu Moy
2013-09-17 9:03 ` Christian Couder
2013-09-17 11:45 ` Duy Nguyen
2013-09-17 17:02 ` Junio C Hamano
2013-09-17 18:12 ` Piotr Krukowiecki
2013-09-17 19:04 ` Junio C Hamano
2013-09-17 19:41 ` Piotr Krukowiecki
2013-09-17 20:47 ` Junio C Hamano [this message]
2013-09-18 2:22 ` Duy Nguyen
2013-11-20 1:41 ` [PATCH] Support pathspec magic :(exclude) and its short form :- Nguyễn Thái Ngọc Duy
2013-11-20 23:48 ` Junio C Hamano
2013-11-21 2:10 ` Duy Nguyen
2013-11-21 18:43 ` Junio C Hamano
2013-09-17 16:23 ` RFC: git bisect should accept "paths-to-be-excluded" Toralf Förster
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=xmqqwqmfw4z8.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=Matthieu.Moy@grenoble-inp$(echo .)fr \
--cc=christian.couder@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=pclouds@gmail$(echo .)com \
--cc=piotr.krukowiecki@gmail$(echo .)com \
--cc=toralf.foerster@gmx$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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