From: Junio C Hamano <gitster@pobox.com>
To: John Goerzen <jgoerzen@complete.org>
Cc: git@vger.kernel.org
Subject: Re: Two bugs with renaming
Date: Wed, 19 Mar 2008 17:51:45 -0700 [thread overview]
Message-ID: <7vwsnyz07y.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <slrnfu37vn.d2i.jgoerzen@katherina.lan.complete.org> (John Goerzen's message of "Wed, 19 Mar 2008 18:21:27 -0500")
John Goerzen <jgoerzen@complete.org> writes:
> # Now here comes bug #1...
Please try 1.5.5-rc0 or newer. I think Linus's unpack_trees() updates,
even though it was sort of a rocky road to get there, addresses this.
Namely, v1.5.5-rc0~25 was the commit that fixed this issue.
> # Set up bug #2
This hasn't been addressed, I think.
next prev parent reply other threads:[~2008-03-20 0:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 23:21 Two bugs with renaming John Goerzen
2008-03-20 0:51 ` Junio C Hamano [this message]
2008-03-20 2:06 ` Jeff King
2008-03-20 2:30 ` John Goerzen
2008-03-20 0:56 ` Jeff King
2008-03-20 1:24 ` Björn Steinbrink
2008-03-20 4:12 ` Linus Torvalds
2008-03-20 4:22 ` Linus Torvalds
2008-03-20 4:45 ` Junio C Hamano
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=7vwsnyz07y.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jgoerzen@complete.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).