From: Rogan Dawes <lists@dawes.za.net>
To: Kris Shannon <kris@shannon.id.au>
Cc: Caleb Cushing <xenoterracide@gmail.com>,
Sitaram Chamarty <sitaramc@gmail.com>,
git@vger.kernel.org
Subject: Re: merge smart enough to adapt to renames?
Date: Sat, 21 Feb 2009 13:12:37 +0200 [thread overview]
Message-ID: <499FE1A5.9020301@dawes.za.net> (raw)
In-Reply-To: <e51f4f550902202048g9a210f0t8fefaee4d8376f6c@mail.gmail.com>
Kris Shannon wrote:
> Rogan Dawes wrote:
>> It seems to me that git is smart enough to figure out where contents get
>> moved to, once. Of course, if you have conflicting moves in the same
>> repo, git's automation falls down. So, if you need to move the "same"
>> file in different repositories to different places, you need to do it
>> via an intermediate repo that will be able to "remember" which movement
>> you chose.
>
> You don't need a whole different repo, branches are good enough.
>
Yes, of course.
Rogan
next prev parent reply other threads:[~2009-02-21 11:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 6:12 merge smart enough to adapt to renames? Caleb Cushing
2009-02-19 14:25 ` Sitaram Chamarty
2009-02-19 19:58 ` Caleb Cushing
2009-02-20 0:36 ` Sitaram Chamarty
2009-02-20 2:17 ` Caleb Cushing
2009-02-20 7:24 ` Rogan Dawes
2009-02-21 4:48 ` Kris Shannon
2009-02-21 11:12 ` Rogan Dawes [this message]
2009-02-22 1:00 ` Caleb Cushing
2009-02-22 17:13 ` Rogan Dawes
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=499FE1A5.9020301@dawes.za.net \
--to=lists@dawes.za.net \
--cc=git@vger.kernel.org \
--cc=kris@shannon.id.au \
--cc=sitaramc@gmail.com \
--cc=xenoterracide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.