From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Elijah Newren <newren@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: Thu, 2 Sep 2010 09:39:39 +1000 [thread overview]
Message-ID: <AANLkTik7eBGJrQ3HEYjesvR9y1PpwUphVvpBmzVCiu6p@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=ma8MLssD_1YeSju7iJucRN9NFzYESJ2rGhyjv@mail.gmail.com>
On Thu, Sep 2, 2010 at 6:54 AM, Elijah Newren <newren@gmail.com> wrote:
>> * en/object-list-with-pathspec (2010-08-26) 2 commits
>> - Make rev-list --objects work together with pathspecs
>> - Add testcases showing how pathspecs are ignored with rev-list --objects
>>
>> Heard that this is still broken?
>
> Are you possibly remembering v1 of the series, which mis-used the
> tree_entry_interesting() API, and was fixed by v2 including extra
> testcases? You merged the latter into pu, so there's no remaining
> issue I know of.
>
> However, if I've missed some email or other report about any other
> breakage, let me know and I'll take a look.
I haven't really used it recently since I'm redoing my series to
support multiple subtree. Will let you know soon if it works (v2
worked last time before the rework).
While at there, how about adding tree exclusion mechanism that you
mentioned in sparse clone? That would be really cool.
--
Duy
next prev parent reply other threads:[~2010-09-01 23:39 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 [this message]
2010-09-04 23:48 ` Elijah Newren
2010-09-05 2:14 ` Nguyen Thai Ngoc Duy
2010-09-05 3:05 ` Elijah Newren
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=AANLkTik7eBGJrQ3HEYjesvR9y1PpwUphVvpBmzVCiu6p@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@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).