From: Caleb Cushing <xenoterracide@gmail.com>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: merge smart enough to adapt to renames?
Date: Thu, 19 Feb 2009 14:58:52 -0500 [thread overview]
Message-ID: <81bfc67a0902191158x5f0f92d1p7e4af2f9cda50a12@mail.gmail.com> (raw)
In-Reply-To: <slrngpqquq.j03.sitaramc@sitaramc.homelinux.net>
> Yes. I maintain two copies of something (in different
> repos) like this...
nice... now the real kicker if I merge from another branch
sunrise/reviewed and redirect it's package.mask to
package.mask/sunrise will git be smart enough to differentiate from
the gentoo.org one and the sunrise one? I think even more important is
how would I even tell it to do that once I've moved the first one.
--
Caleb Cushing
http://xenoterracide.blogspot.com
next prev parent reply other threads:[~2009-02-19 20:00 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 [this message]
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
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=81bfc67a0902191158x5f0f92d1p7e4af2f9cda50a12@mail.gmail.com \
--to=xenoterracide@gmail.com \
--cc=git@vger.kernel.org \
--cc=sitaramc@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).