Hi List!
When importing a git fast import file, the master branch is silently
changed to trunk, to match the fossil default.
However, when exported back out the reverse conversion does not apply.
This is not good, because fossil is effectively re-writing history.
But what is worse is that the
On 09/02/2017 15:06, Joerg Sonnenberger wrote:
> On Thu, Feb 09, 2017 at 01:47:43PM +, Roy Marples wrote:
>> Hi List!
>>
>> In fossil I have this: branch-1.7, tag-1.2
>> But when I export I get this: branch_1_7, tag_1_2
>>
>> Why is the name mangled like so? Surely the original names should be
On Wed, May 21, 2014 at 06:08:25PM -0400, Ronald Perrella wrote:
> Hi Folks,
>
> I apologize if this appears to be a repost. I'm not a frequent mailing list
> user.
>
> I've uploaded a Jenkins Plugin for Fossil to my GitHub repository for those
> who might have an interest. It is Java
On 09/02/2017 14:39, Roy Marples wrote:
> Exporting tags using fossil-1.37 I see this in the resultant import:
>
> tagged by
>
> whereas is should be
>
> tagged by Roy Marples
Patch attached to fix this.
Roy
Export tag comitter.
--- src/export.c.orig
On Thu, Feb 09, 2017 at 10:13:21AM -0500, Richard Hipp wrote:
> On 2/9/17, Joerg Sonnenberger wrote:
> >
> > I disagree. The problem is not on the fossil side and I am not even sure
> > the "specification" of fastexport disallows it. It's really a git issue.
> >
>
> I agree with
On 2/9/17, Joerg Sonnenberger wrote:
>
> I disagree. The problem is not on the fossil side and I am not even sure
> the "specification" of fastexport disallows it. It's really a git issue.
>
I agree with you, Joerg. But if the problem is going to be fixed, it
will probably have to
On Thu, Feb 09, 2017 at 01:47:43PM +, Roy Marples wrote:
> Hi List!
>
> In fossil I have this: branch-1.7, tag-1.2
> But when I export I get this: branch_1_7, tag_1_2
>
> Why is the name mangled like so? Surely the original names should be
> preserved.
It's currently preserving only
On Thu, Feb 09, 2017 at 01:15:51PM +, Roy Marples wrote:
> Hi List!
>
> I have a few repos which I sync to git. However, one of them I noticed
> is no longer syncing tags. The fossil repo is here:
> https://roy.marples.name/projects/dhcpcd
>
> Using fossil-1.37
>
> fossil export --git
On Feb 9, 2017, at 6:47 AM, Roy Marples wrote:
>
> In fossil I have this: branch-1.7, tag-1.2
> But when I export I get this: branch_1_7, tag_1_2
>
> Why is the name mangled like so? Surely the original names should be
> preserved.
I assume it’s a “feature” of fossil export
On Feb 9, 2017, at 6:15 AM, Roy Marples wrote:
>
> error: multiple updates for ref 'refs/tags/dhcpcd_6_11_3' not allowed.
> git tag
Fossil allows a given tag to refer to multiple checkin IDs, but Git does not,
so it complains on trying to import it.
At the moment, your only
Exporting tags using fossil-1.37 I see this in the resultant import:
tagged by
whereas is should be
tagged by Roy Marples
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
Thus said john lunzer on Sun, 05 Feb 2017 13:06:04 -0500:
> Here is the test sequence:
>
> cd fossils
> fossil new testrepo.fossil
> mkdir ../testrepo
> cd ../testrepo
> fossil open ../fossils/testrepo.fossil
> fossil branch new myfirstbranch trunk
> fossil commit --allow-empty --branch
Hi List!
In fossil I have this: branch-1.7, tag-1.2
But when I export I get this: branch_1_7, tag_1_2
Why is the name mangled like so? Surely the original names should be
preserved.
Roy
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
Hi List!
I have a few repos which I sync to git. However, one of them I noticed
is no longer syncing tags. The fossil repo is here:
https://roy.marples.name/projects/dhcpcd
Using fossil-1.37
fossil export --git dhcpcd.fossil > dhcpcd.export
git init dhcpcd-git
cd dhcpcd-git
git fast-import
14 matches
Mail list logo