git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Elijah Newren <newren@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2010, #01; Wed, 1)
Date: Wed, 1 Sep 2010 14:54:45 -0600	[thread overview]
Message-ID: <AANLkTi=ma8MLssD_1YeSju7iJucRN9NFzYESJ2rGhyjv@mail.gmail.com> (raw)
In-Reply-To: <7vaao15jk2.fsf@alter.siamese.dyndns.org>

> * 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.

> * en/tree-walk-optim (2010-08-26) 4 commits
>  - diff_tree(): Skip skip_uninteresting() when all remaining paths interesting
>  - tree_entry_interesting(): Make return value more specific
>  - tree-walk: Correct bitrotted comment about tree_entry()
>  - Document pre-condition for tree_entry_interesting
>
> I think the idea is sound.  For a patch that touches fairly core part of
> the system, it came a bit late in the cycle, though.

I agree, both this and the en/object-list-with-pathspec series
probably make sense to wait for 1.7.4.

  parent reply	other threads:[~2010-09-01 20:54 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 [this message]
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
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='AANLkTi=ma8MLssD_1YeSju7iJucRN9NFzYESJ2rGhyjv@mail.gmail.com' \
    --to=newren@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).