From: Sam Vilain <sam@vilain.net>
To: Eric Wong <normalperson@yhbt.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Is this an acceptable workflow in git-svn, or a user error?
Date: Sun, 10 Jun 2007 19:49:14 +1200 [thread overview]
Message-ID: <466BACFA.1000704@vilain.net> (raw)
In-Reply-To: <466BABFB.8080208@vilain.net>
Sam Vilain wrote:
> Eric Wong wrote:
>
>>> Is my understanding correct?
>>>
>> Yes. Since dcommit uses rebase, it'll rewrite history.
>>
> Maybe these new lightweight annotations could be a way around that?
>
Actually I don't think that will work either unless you start
encapsulating extra git information (author/committer email/timestamps)
in the svn commit somewhere, so that someone else fetching the commits
from svn directly will end up with the same git commitid. And then
there's still the issue of merges.
Sam.
prev parent reply other threads:[~2007-06-10 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-09 19:10 Is this an acceptable workflow in git-svn, or a user error? Junio C Hamano
2007-06-09 19:38 ` Eric Wong
2007-06-10 7:44 ` Sam Vilain
2007-06-10 7:49 ` Sam Vilain [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=466BACFA.1000704@vilain.net \
--to=sam@vilain.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=normalperson@yhbt.net \
/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).