From: Jeff King <peff@peff.net>
To: David Copeland <davetron5000@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: move files between disparate repos and maintain version history
Date: Tue, 3 Mar 2009 14:27:43 -0500 [thread overview]
Message-ID: <20090303192743.GA3530@coredump.intra.peff.net> (raw)
In-Reply-To: <f95d47890903031008s36873f6ex94c7096f79cd6de@mail.gmail.com>
On Tue, Mar 03, 2009 at 01:08:17PM -0500, David Copeland wrote:
> 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?
I know very little about git-svn. But you could test your theory by
checking the dates between the penultimate and ultimate steps.
-Peff
prev parent reply other threads:[~2009-03-03 19:29 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
2009-03-03 19:22 ` Peter Baumann
2009-03-03 19:27 ` Jeff King [this message]
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=20090303192743.GA3530@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=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).