From: "H. Peter Anvin" <hpa@zytor.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Moved files and merges
Date: Fri, 02 Sep 2005 16:59:16 -0700 [thread overview]
Message-ID: <4318E754.9000703@zytor.com> (raw)
I currently have two klibc trees,
rsync://rsync.kernel.org/pub/scm/libs/klibc/klibc.git
and
rsync://rsync.kernel.org/pub/scm/libs/klibc/klibc-kbuild.git
One of the differences between the trees is that a bunch of files have
been rearranged. Unfortunately, it seems that whenever I try to merge
one into the other, using cg-update from the former branch to the
latter, if any of these files have been touched, cg-update fails, and I
have to:
- touch these files in the "old location" manually;
- manually apply the change to the new location (and, sad to say, I
haven't even figured out how to take the numbers cg-update spits out and
feed them to cg-diff);
- commit.
Is there any way I can record in the repository that these files are
actually moved files, and that the merge should apply the patch elsewhere?
Thanks,
-hpa
next reply other threads:[~2005-09-02 23:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 23:59 H. Peter Anvin [this message]
2005-09-03 0:20 ` Moved files and merges Martin Langhoff
2005-09-04 4:14 ` H. Peter Anvin
2005-09-03 1:36 ` Junio C Hamano
2005-09-03 8:25 ` Junio C Hamano
2005-09-03 18:06 ` Fredrik Kuivinen
2005-09-03 18:53 ` Junio C Hamano
2005-09-03 18:46 ` Junio C Hamano
2005-09-03 19:05 ` Sam Ravnborg
2005-09-03 19:32 ` Junio C Hamano
2005-09-03 22:03 ` Sam Ravnborg
2005-09-04 7:32 ` Junio C Hamano
2005-09-04 18:28 ` Daniel Barkalow
2005-09-04 19:10 ` Junio C Hamano
2005-09-05 15:16 ` H. Peter Anvin
2005-09-05 15:47 ` Linus Torvalds
2005-09-05 16:37 ` H. Peter Anvin
2005-09-05 18:08 ` Junio C Hamano
2005-09-05 18:33 ` Junio C Hamano
2005-09-05 18:43 ` H. Peter Anvin
2005-09-04 8:27 ` Junio C Hamano
2005-09-03 19:21 ` Fredrik Kuivinen
2005-09-03 18:59 ` Sam Ravnborg
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=4318E754.9000703@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.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).