> --rename-master renames master
> --rename-trunk renames trunk
> We should strive to keep the command line UI sane.
In my opinion, preserving the long-standing default import target
branch as "trunk" is reasonable, whether we change the semantics of
"--rename-trunk" option or not.
The notion of
On 13/02/2017 11:12, Jan Nijtmans wrote:
> 2017-02-13 12:09 GMT+01:00 Roy Marples:
>> Is the value displayed in the timeline?
> Yes
>> I'm also unsure about overloading the meaning of tag value . the ui
>> indicates it can be set via the command line so could someone be using
>> it for
2017-02-13 12:09 GMT+01:00 Roy Marples:
> Is the value displayed in the timeline?
Yes
> I'm also unsure about overloading the meaning of tag value . the ui
> indicates it can be set via the command line so could someone be using
> it for something else to store in fossil?
For some tags, like
On 13/02/2017 10:42, Jan Nijtmans wrote:
> 2017-02-13 4:50 GMT+01:00 Roy Marples:
>> 3 has now been implemented in the roy-export branch.
>> Turned out to be quite easy. A database rebuild is required though as an
>> extra field has been added to the tagxref table.
>
> Thanks, Roy! I looked at
On 13/02/2017 09:49, Roy Marples wrote:
>>> * tag comments are imported and exported [2]
>>
>> ?? How does one enter a tag comment from the Fossil command line or
>> this is an import/export only feature?
fossil tag add --comment "A tag test comment" tagtest current
now works.
Roy
2017-02-13 4:50 GMT+01:00 Roy Marples:
> 3 has now been implemented in the roy-export branch.
> Turned out to be quite easy. A database rebuild is required though as an
> extra field has been added to the tagxref table.
Thanks, Roy! I looked at your implementation: cards have to
be in
On 13/02/2017 06:47, Artur Shepilko wrote:
>> * no more silent renaming of master vs trunk [1]
>
> "fossil import --rename-trunk" already allows a choice for a Fossil
> branch name to receive Git's "master" branch.
> A bug was missed in src/import.c:~567 if( fossil_strcmp(z,
> "master")==0 ) z
> * no more silent renaming of master vs trunk [1]
"fossil import --rename-trunk" already allows a choice for a Fossil
branch name to receive Git's "master" branch.
A bug was missed in src/import.c:~567 if( fossil_strcmp(z,
"master")==0 ) z = "trunk";
In src/import.c this option is stored in
On 13/02/17 01:23, Roy Marples wrote:
> On 13/02/17 01:01, Roy Marples wrote:
>> 1) add an option to (or to not) export tags. The git default is not to,
>> I'm tempted to make this the fossil default as well. See *.
>
> This is wrong. Git has no such option.
>
>> 2) maintain a file of tags so we
On 13/02/17 01:01, Roy Marples wrote:
> 1) add an option to (or to not) export tags. The git default is not to,
> I'm tempted to make this the fossil default as well. See *.
This is wrong. Git has no such option.
> 2) maintain a file of tags so we only export tags generated at the
> fossil side,
Hi List
So git fast-export only exports anointed tags - they usually have a comment.
Fossil tags don't have comments.
This is slightly problematic for a bridge. Because we add all tags to
the fast-export file they will overwrite tags at the other end. As such,
the git repos that sync to the git
11 matches
Mail list logo
