From: Elijah Newren <newren@gmail.com>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Sep 2010, #01; Wed, 1)
Date: Sat, 4 Sep 2010 21:05:51 -0600 [thread overview]
Message-ID: <AANLkTimMbTNSgaep-hQ5NObgNMVNk76FmJSbCy7+B6i5@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinoegtf1G2FxfT_vvQRRMMuyNMc7zM5SY8oG_rY@mail.gmail.com>
On Sat, Sep 4, 2010 at 8:14 PM, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:
> On Sun, Sep 5, 2010 at 9:48 AM, Elijah Newren <newren@gmail.com> wrote:
>> On Wed, Sep 1, 2010 at 5:39 PM, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:
>>> While at there, how about adding tree exclusion mechanism that you
>>> mentioned in sparse clone? That would be really cool.
>>
>> Tree exclusion or commit exclusion? I think I have the former working
>> (I'll post a patch series soon), but not the latter yet.
>>
>
> Yeah.. I'm looking at it now. By tree exclusion, I meant negative
> pathspec. Something like "traverse anything in 't' except t/t9700". I
> can see you are getting real close to that.
Ah, nope, I haven't tackled that at all and hadn't planned to anytime soon.
next prev parent reply other threads:[~2010-09-05 3:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 19:51 What's cooking in git.git (Sep 2010, #01; Wed, 1) Junio C Hamano
2010-09-01 20:22 ` Ævar Arnfjörð Bjarmason
2010-09-01 20:54 ` Elijah Newren
2010-09-01 23:39 ` Nguyen Thai Ngoc Duy
2010-09-04 23:48 ` Elijah Newren
2010-09-05 2:14 ` Nguyen Thai Ngoc Duy
2010-09-05 3:05 ` Elijah Newren [this message]
2010-09-02 16:26 ` Junio C Hamano
2010-09-02 8:52 ` Matthieu Moy
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=AANLkTimMbTNSgaep-hQ5NObgNMVNk76FmJSbCy7+B6i5@mail.gmail.com \
--to=newren@gmail.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 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 NNTP newsgroup(s).