git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kris Shannon <kris@shannon.id.au>
To: Rogan Dawes <lists@dawes.za.net>
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 15:48:01 +1100	[thread overview]
Message-ID: <e51f4f550902202048g9a210f0t8fefaee4d8376f6c@mail.gmail.com> (raw)
In-Reply-To: <499E5A9C.6090900@dawes.za.net>

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.

git checkout gentoo-integration
git pull gentoo

git checkout sunrise-integration
git pull sunrise

git checkout master
git merge gentoo
git merge sunrise

The integration branches can remember your local changes to
the remotes (like the move of packages.mask)

  reply	other threads:[~2009-02-21  4:49 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 [this message]
2009-02-21 11:12             ` Rogan Dawes
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=e51f4f550902202048g9a210f0t8fefaee4d8376f6c@mail.gmail.com \
    --to=kris@shannon.id.au \
    --cc=git@vger.kernel.org \
    --cc=lists@dawes.za.net \
    --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 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).