From: Junio C Hamano <gitster@pobox.com>
To: Nanako Shiraishi <nanako3@lavabit.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Remove unused t/t8005/iso8859-5.txt file
Date: Sun, 30 Aug 2009 13:14:38 -0700 [thread overview]
Message-ID: <7v3a79dpox.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 20090829170809.6117@nanako3.lavabit.com
Nanako Shiraishi <nanako3@lavabit.com> writes:
> Quoting Junio C Hamano <gitster@pobox.com>
>
>> Out of curiosity, how did you find this?
>
> Soon after you posted your original in
> http://thread.gmane.org/gmane.comp.version-control.git/121881, I applied
> it to my tree, and I have been running 'git pull --rebase' for ever. I
> noticed that rebase didn't remove the commit, even after your 54bc13c.
>
> Today I found that the rebased patch only removed that file. The real
> question is how you lost the deletion of the file when you applied. What
> happened?
My stupidity, and a little bit of danger in trusting "am -3" blindly.
The patch sent to the list was against the master, but the actual commit
created, 54bc13c, was on maint. Back then, there was a commit in master
but not in maint that stopped using cp1251.txt and started using
iso8859-5.txt instead.
Because maint did not have iso8859-5.txt (which the patch wanted to
remove), when "am -3" did its fake 3-way merge, the removal of the path
did not even conflict. It was the case of "neither side wants to have
this file". As the result, cp1251.txt was left in the tree (which is
half-Ok, even though the updated test never looked at it anymore), and
merging the result back to master did not touch iso8859-5.txt.
prev parent reply other threads:[~2009-08-30 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-29 7:16 [PATCH] Remove unused t/t8005/iso8859-5.txt file Nanako Shiraishi, しらいし ななこ
2009-08-29 7:48 ` Junio C Hamano
2009-08-29 8:08 ` Nanako Shiraishi
2009-08-30 20:14 ` 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=7v3a79dpox.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=nanako3@lavabit.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).