From: David Copeland <davetron5000@gmail.com>
To: git@vger.kernel.org
Subject: Re: move files between disparate repos and maintain version history
Date: Tue, 3 Mar 2009 13:08:17 -0500 [thread overview]
Message-ID: <f95d47890903031008s36873f6ex94c7096f79cd6de@mail.gmail.com> (raw)
In-Reply-To: <20090303171835.GB454@coredump.intra.peff.net>
The patch file looks correct. I'm wondering if this is a result of
both repos being connected to svn?
my process was:
- format patch
- go to other repo
- git svn rebase
- apply patch
- git svn dcommit
Could dcommit change the dates since, to svn, they are appear as
commits right now?
Dave
On Tue, Mar 3, 2009 at 12:18 PM, Jeff King <peff@peff.net> wrote:
> On Tue, Mar 03, 2009 at 11:58:42AM -0500, David Copeland wrote:
>
>> The first option worked, insomuch the history of diffs is preserved,
>> but the dates are all today.
>
> That's odd. It works fine here. Can you confirm that the correct dates
> in the "patches" file (i.e., the output of format-patch)? What are you
> using to look at the patches? Note that gitk will show you both the
> "committer" and the "author" fields. The "author" field should have the
> original author and time of the patch, but the "committer" will be you,
> today.
>
>> The second option was a little over my head; is the idea there that
>> you are setting up a branch that has ONLY the files I care about (with
>> all their history), and then I pull from the other repo as if they are
>> related? That seems like it might preserve the dates...
>
> Yes, that is exactly what is happening in the second example.
>
> -Peff
>
next prev parent reply other threads:[~2009-03-03 18:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 20:30 move files between disparate repos and maintain version history davetron5000
2009-03-03 4:13 ` Jeff King
2009-03-03 16:58 ` David Copeland
2009-03-03 17:18 ` Jeff King
2009-03-03 18:08 ` David Copeland [this message]
2009-03-03 19:22 ` Peter Baumann
2009-03-03 19:27 ` Jeff King
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=f95d47890903031008s36873f6ex94c7096f79cd6de@mail.gmail.com \
--to=davetron5000@gmail.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).