[fossil-users] Names in imported git repositories

[org.fossil-sc...@io7m.com]

Hello.

I'm attempting to import a test repository from git. Unfortunately, the
names used in the resulting fossil commits are the *email addresses* of
the original committers.

Is it possible to tell fossil that commits should be "assigned" to
specific user names in the resulting fossil repository?
_______________________________________________
fossil-users mailing list
fossil...@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[Martin Gagnon]

In your git log, does it use email address too? If yes it look to be git fault.

I use to convert a cvs repository to git and then to fossil and name was ok. Probably because they were originated from cvs and they were not email.

--
Martin G.

--
Martin

[org.fossil-sc...@io7m.com]

On Thu, 15 Mar 2012 09:54:56 -0400
Martin Gagnon <eme...@gmail.com> wrote:

> In your git log, does it use email address too? If yes it look to be
> git fault.

It gives the username followed by the address, if that's what you mean:

$ git log
commit 2984eef58e059db374b17183f69b411ae518a505
Author: tr-git <g...@io7m.com>
Date: Wed Mar 14 23:37:32 2012 +0000

Test commit

The commits in the fossil repository all appear to come from
"g...@io7m.com" as opposed to "tr-git".

[Dmitry Chestnykh]

On 03/15/2012 02:38 PM, org.fossil-sc...@io7m.com wrote:
> Is it possible to tell fossil that commits should be "assigned" to
> specific user names in the resulting fossil repository?

When I converted my repos, I just did a global search/replace in the
file exported from git.

--
Dmitry Chestnykh
http;//www.codingrobots.org

[org.fossil-sc...@io7m.com]

On Sat, 17 Mar 2012 03:11:56 +0100
Dmitry Chestnykh <dmi...@codingrobots.com> wrote:

> On 03/15/2012 02:38 PM, org.fossil-sc...@io7m.com wrote:
> > Is it possible to tell fossil that commits should be "assigned" to
> > specific user names in the resulting fossil repository?
>
> When I converted my repos, I just did a global search/replace in the
> file exported from git.
>

That's fine. Just wanted to be sure that this wasn't a bug.