From: Junio C Hamano <gitster@pobox.com>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org, gitster@pobox.com
Subject: Re: [BUGFIX PATCH 2/2] fast-export: use an unsorted string list for extra_refs
Date: Sun, 23 Nov 2008 17:07:09 -0800 [thread overview]
Message-ID: <7vwseund8i.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20081123180353.GM4746@genesis.frugalware.org> (Miklos Vajna's message of "Sun, 23 Nov 2008 19:03:53 +0100")
Thanks both; I do not have time to actually double-check and apply for the
next 36 hours or so, though.
prev parent reply other threads:[~2008-11-24 1:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 2:29 git fast-export problem with tags Miklos Vajna
2008-11-22 18:22 ` [PATCH] Add new testcase to show fast-export does not always exports all tags Miklos Vajna
2008-11-23 11:55 ` [PATCH 1/2] Simplify and fix t9301 Johannes Schindelin
2008-11-23 11:55 ` [BUGFIX PATCH 2/2] fast-export: use an unsorted string list for extra_refs Johannes Schindelin
2008-11-23 18:03 ` Miklos Vajna
2008-11-24 1:07 ` Junio C Hamano [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=7vwseund8i.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=vmiklos@frugalware.org \
/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).