From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Sebastian Thiel <byronimo@gmail.com>,
Alex Riesen <raa.lkml@gmail.com>,
git@vger.kernel.org
Subject: Re: Bug Report ( including test script ): Non-Fastforward merges misses directory deletion
Date: Thu, 18 Feb 2010 22:23:42 -0800 [thread overview]
Message-ID: <7v3a0xwxox.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20100219055721.GC22645@coredump.intra.peff.net> (Jeff King's message of "Fri\, 19 Feb 2010 00\:57\:21 -0500")
Jeff King <peff@peff.net> writes:
> This was introduced by Alex's 4a92d1b (Add remove_path: a function to
> remove as much as possible of a path, 2008-09-27), which ironically
> complained about bugs in the code it was replacing. :)
Good catch. I wish all bugs are this easy ;-)
Thanks.
next prev parent reply other threads:[~2010-02-19 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 10:00 Bug Report ( including test script ): Non-Fastforward merges misses directory deletion Sebastian Thiel
2010-02-18 11:43 ` Sebastian Thiel
2010-02-19 5:57 ` Jeff King
2010-02-19 6:23 ` Junio C Hamano [this message]
2010-02-19 7:40 ` Alex Riesen
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=7v3a0xwxox.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=byronimo@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=raa.lkml@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).