Re: [fossil-users] Git Tag comments

> * 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

Re: [fossil-users] Git Tag comments

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

Re: [fossil-users] Git Tag comments

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,

[fossil-users] Git Tag comments

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

Re: [fossil-users] Fossil SCGI Server Regression (from 1.36 to 1.37)

On 2/12/17, Thomas Bilk wrote: > > I guess there was a regression introduced somewhere between [8b03934e] > and [fb4b87d9]. Would you be willing to bisect for us? -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list

[fossil-users] Fossil SCGI Server Regression (from 1.36 to 1.37)

Hi all. I was finally upgrading my fossil server and encountered what I assume to be a regression. I am using the fossil server with scgi behind an nginx web server. I am hosting a directory with fossil repositories. These is my configuration: The fossil server is started with this fossil server

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

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

[fossil-users] using Fossil & Github's PRs

Hello! Fossil is great and cool to use, Git(hub) is popular, so wondering what to do? Is there some smooth workflow allowing one to easily contribute to e.g. Github projects by using the usual scenario of: a) cloning the upstream repo b) creating feature branch c) commit contributed changes