From: Elijah Newren <newren@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Johannes.Schindelin@gmx.de, kusmabite@gmail.com
Subject: Re: [PATCH v2] fast-export: Add a --tag-of-filtered-object option for newly dangling tags
Date: Thu, 25 Jun 2009 22:45:13 -0600 [thread overview]
Message-ID: <51419b2c0906252145pe174d1diddee9ed81413af74@mail.gmail.com> (raw)
In-Reply-To: <7vd48wazhu.fsf@alter.siamese.dyndns.org>
Hi,
Thanks for the detailed feedback and suggestions. I'll send a new
patch series shortly, which I believe addresses all your suggestions
and requests (and opens up a new issue), but there is one item in
particular I wanted to respond to...
On Mon, Jun 22, 2009 at 12:34 PM, Junio C Hamano<gitster@pobox.com> wrote:
> Also, are you absolutely sure that your revs is always limited at this
> point? Otherwise, the parents of this commit are queued in rev->list,
> expecting somebody else to later pick them up and further process, but
> there is nobody who does that in your codepath as far as I can see. What
> will happen to these parent commits?
revs was not limited, but should have been. Inside setup_revisions,
revs->limited is set if revs->topo_order is, but unfortunately we
weren't setting revs->topo_order until after the call to
setup_revisions. So, as you suggest, my code caused the parents of
the rewritten commit to needlessly get queued up and left around, with
no one to process them. Oops.
Elijah
next prev parent reply other threads:[~2009-06-26 4:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 13:06 A few fast export fixups -- round 2 newren
2009-06-22 13:06 ` [PATCH v2] fast-export: Omit tags that tag trees newren
2009-06-22 18:33 ` Junio C Hamano
2009-06-22 13:06 ` [PATCH v2] fast-export: Make sure we show actual ref names instead of "(null)" newren
2009-06-22 18:34 ` Junio C Hamano
2009-06-22 13:06 ` [PATCH v2] fast-export: Do parent rewriting to avoid dropping relevant commits newren
2009-06-22 13:06 ` [PATCH v2] fast-export: Add a --tag-of-filtered-object option for newly dangling tags newren
2009-06-22 18:34 ` Junio C Hamano
2009-06-26 4:45 ` Elijah Newren [this message]
2009-06-22 13:06 ` [PATCH v2] Add new fast-export testcases newren
2009-06-22 13:06 ` [PATCH v2] fast-export: Document the fact that git-rev-list arguments are accepted newren
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=51419b2c0906252145pe174d1diddee9ed81413af74@mail.gmail.com \
--to=newren@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kusmabite@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).