From: "Pico Geyer" <picogeyer@gmail.com>
To: git@vger.kernel.org
Subject: Re: Help using Git(-svn) for specific use case
Date: Tue, 16 Sep 2008 00:53:05 +0200 [thread overview]
Message-ID: <aa2b76740809151553v70206abhe02d0859fdc62378@mail.gmail.com> (raw)
In-Reply-To: <20080915214740.GI28210@dpotapov.dyndns.org>
Thanks guys for your replies and advice.
I'm going to be trying to configure such a setup tomorrow.
I'll probably have more questions :-)
Regards,
Pico Geyer
On Mon, Sep 15, 2008 at 11:47 PM, Dmitry Potapov <dpotapov@gmail.com> wrote:
> On Mon, Sep 15, 2008 at 11:15:59PM +0200, Michael J Gruber wrote:
>> Sverre Rabbelier venit, vidit, dixit 15.09.2008 22:59:
>> >
>> > I thought this was fixed in a more recent version of git-svn? Didn't
>> > it even work both ways?
>>
>> Kind of. You can't fake a different author when committing to svn.
>
> This is not exactly correct as you can fake author if you have the right
> to change the svn:author property (or what is its name?), but by default
> this is not allowed to anyone, and git-svn does not support this method
> anyway.
>
>> But
>> "--add-author-from" makes dcommit embed the author in the svn commit
>> message (if there's no from nor sob), and "--use-log-author" makes fetch
>> look for that info and use it.
>
> Yes, it works. And it is very useful especially you are going eventually
> convert your SVN repository in Git (so all authorship information will
> be retain). Probably, I should have mentioned this possibility.
>
> Thanks,
> Dmitry
>
next prev parent reply other threads:[~2008-09-15 22:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 12:50 Help using Git(-svn) for specific use case Pico Geyer
2008-09-15 15:12 ` Michael J Gruber
2008-09-15 19:55 ` Dmitry Potapov
2008-09-15 20:59 ` Sverre Rabbelier
2008-09-15 21:15 ` Michael J Gruber
2008-09-15 21:47 ` Dmitry Potapov
2008-09-15 22:53 ` Pico Geyer [this message]
2008-09-17 14:09 ` Pico Geyer
2008-09-18 5:56 ` Dmitry Potapov
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=aa2b76740809151553v70206abhe02d0859fdc62378@mail.gmail.com \
--to=picogeyer@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).