Re: [fossil-users] fossil export handling of trunk differs from import

2017-02-12 Thread Roy Marples
On 10/02/17 17:52, Roy Marples wrote: > On 09/02/2017 21:42, Roy Marples wrote: >> 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

Re: [fossil-users] fossil export handling of trunk differs from import

2017-02-10 Thread Roy Marples
On 10/02/2017 19:10, Joe Mistachkin wrote: > > Roy Marples wrote: >> >> fossil import --rename-master trunk >> fossil export --rename-trunk master >> > > As a matter of my personal preferences and taste, I really like the > idea of NOT doing "magic branch renaming" by default and adding the >

Re: [fossil-users] fossil export handling of trunk differs from import

2017-02-10 Thread Joe Mistachkin
Roy Marples wrote: > > fossil import --rename-master trunk > fossil export --rename-trunk master > As a matter of my personal preferences and taste, I really like the idea of NOT doing "magic branch renaming" by default and adding the above new options. What kind of backward compatibility

Re: [fossil-users] fossil export handling of trunk differs from import

2017-02-10 Thread Roy Marples
On 09/02/2017 21:42, Roy Marples wrote: > 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

[fossil-users] fossil export handling of trunk differs from import

2017-02-09 Thread Roy Marples
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