From: Jon Seymour <jon.seymour@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Fix rename/copy when dealing with temporarily broken pairs.
Date: Tue, 14 Jun 2005 02:24:16 +1000 [thread overview]
Message-ID: <2cfc4032050613092462d3a456@mail.gmail.com> (raw)
In-Reply-To: <7vwtp0p6tz.fsf@assigned-by-dhcp.cox.net>
G'day Junio,
On 6/12/05, Junio C Hamano <junkio@cox.net> wrote:
> When rename/copy uses a file that was broken by diffcore-break
> as the source, and the broken filepair gets merged back later,
> the output was mislabeled as a rename. In this case, the source
> file ends up staying in the output, so we should label it as a
> copy instead.
I've got a patch series that renames a file, but the patches generated by your
git-format-patch-script fail to rename the file to the new name.
I wondered if this patch might fix it, but it doesn't seem to.
Here's a hunk from the patch:
diff --git a/epoch.c b/traversal.c
similarity index 100%
rename from epoch.c
rename to traversal.c
--- a/epoch.c
+++ b/traversal.c
@@ -14,7 +14,7 @@
#include "cache.h"
#include "commit.h"
-#include "epoch.h"
+#include "traversal.h"
struct fraction {
BIGNUM numerator;
What tool am I meant to be using to apply the patch?
I am currently using "patch -p1"
jon.
next prev parent reply other threads:[~2005-06-13 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 9:53 [PATCH 5/3] read-tree: loosen too strict index requirements Junio C Hamano
2005-06-12 3:55 ` [PATCH] Fix rename/copy when dealing with temporarily broken pairs Junio C Hamano
2005-06-13 16:24 ` Jon Seymour [this message]
2005-06-13 17:58 ` Petr Baudis
2005-06-13 21:01 ` Junio C Hamano
2005-06-13 22:17 ` Jon Seymour
2005-06-12 3:57 ` [PATCH] Add --diff-filter= output restriction to diff-* family 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=2cfc4032050613092462d3a456@mail.gmail.com \
--to=jon.seymour@gmail.com \
--cc=git@vger.kernel.org \
--cc=jon@blackcubes.dyndns.org \
--cc=junkio@cox.net \
/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).