From: Phillip Susi <psusi@ubuntu.com>
To: Duy Nguyen <pclouds@gmail.com>, Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Filter log based on paths NOT touched
Date: Mon, 25 Nov 2013 23:34:36 -0500 [thread overview]
Message-ID: <529424DC.6030107@ubuntu.com> (raw)
In-Reply-To: <CACsJy8DR-ckmZ8Ey9Gh1fhv17_+mRPmeLdj_7LoCnvc9fnnpTg@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 11/25/2013 10:13 PM, Duy Nguyen wrote:
> There's a difference between "skip commits that touch anything
> directory foo even if it also touches something outside of foo" and
> "skip commits that _only_ touches something in foo". Not sure which
> way Phillip wants here. Negative pathspec only supports the latter.
> The former needs a new option in rev-list, because the logic to
> consider a commit not a match if it matches a pathspec is out of
> tree_entry_interesting()'s control.
I'm looking for the latter. Specifically I'm trying to see what changes to the upstream code a debian package has made so I need to ignore commits that only change things in debian/.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBCgAGBQJSlCTcAAoJEJrBOlT6nu75jUQIAJOybMyXE6lr4y4aX6od02Rn
lINvPVC1Xub2E1lsofIB+N4QvZDRWlIJOIcj3GRqirzUcNBaIOUxUW4+UV7KgMQH
wmImS8DdBgrkI8Sompe9B0gqd4lmB2mzTutQfOzdEZ/ZOU50935daYboK//X7zM/
vSmumJpRwNfw1BKyuxVpAQ8Ablo9yUu2cswLKJPSKyQkT9d/AJn07LE5/DKZORQN
RD3r94kToftgTfsQTJbNpPujJ5nVHwVmiC44Qghdquj54l++ai5Xs2wRU3Za3i+O
ts7Tn5Lrw+pFAT5Lnt0v8Yedp7fVgjRhIsNEDIVlgNuHevP/oBOXIxuLJBlCBIE=
=AYYO
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2013-11-26 4:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 20:20 Filter log based on paths NOT touched Phillip Susi
2013-11-25 20:35 ` Junio C Hamano
2013-11-26 3:13 ` Duy Nguyen
2013-11-26 4:34 ` Phillip Susi [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=529424DC.6030107@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@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.
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.