[fossil-users] Introducing FossGit -- a new CLI tool for conveniently mirroring Fossil to Git.
Introducing FossGit: "Good news, everyone! I just published a new gem!" - Dr. Farnsworth As announced here, I published a simple new utility called FossGit for creating and maintaining Git mirrors of Fossil repositories: https://twitter.com/apotheon/status/813072784238804993 The rubygems page is: https://rubygems.org/gems/fossgit The Fossil repository is: https://fossrec.com/u/apotheon/fossgit/index.cgi/index The Git mirror (created/maintained by FossGit itself) is: https://github.com/apotheon/fossgit/ It's basically a glorified shell script at this time. It will probably become much more at some point. Happy holidays. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] incorrect user info in export --git
On Sun, Dec 25, 2016 at 12:22:43PM -0500, Ron W wrote: > > I only use git when I have to, generally when a project requires submitting > pull requests. In that case, I still track my local changes in Fossil. Then > I pull the latest into my clone of the git repo, merge the changes into my > work space, rebuild, retest abd repeat as needed. Then I commit the "final" > changes to my clone and send the pull request. That sounds like a use case for what I've built, plus functionality going the other way (Git->Fossil), which I haven't built (yet). Of course, all this stuff is handled by export and import commands for both Fossil and Git, but I built something to mirror Fossil repositories to Git repositories so I could simplify my life somewhat when doing that. > > At work, the controls software group uses Fossil "internally", but the > company is still "standardized" on SVN (because the IT group's vision is > for "thin client" PCs that are fully interchangeable, which doesn't work > for my group because we need specialized tool chains that don't "play well" > with IT's vision). We use Fossil for our day-to-day work, only committing > releases to SVN. It seems like you have need of tools for import/export mirroring with Subversion, too. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] incorrect user info in export --git
On Sun, Dec 25, 2016 at 7:00 AM,wrote: > > Date: Sun, 25 Dec 2016 05:11:28 + > From: Chad Perrin > Subject: Re: [fossil-users] incorrect user info in export --git > > On Sat, Dec 24, 2016 at 12:47:43PM -0800, bch wrote: > > On Dec 24, 2016 10:05, "Stephan Beal" wrote: > > > > On Sat, Dec 24, 2016 at 6:42 PM, Chad Perrin wrote: > > > > > I hope the lack of responses to my questions was because of the holiday > > > season > > > > > > Or maybe interest in git is slowly dying off ;). > > > > > > Ever hopeful... > > I wish, but from what I've seen that's not happening in the wider world. > I'd easily believe people who start using Fossil end up losing interest > in Git, though. > I only use git when I have to, generally when a project requires submitting pull requests. In that case, I still track my local changes in Fossil. Then I pull the latest into my clone of the git repo, merge the changes into my work space, rebuild, retest abd repeat as needed. Then I commit the "final" changes to my clone and send the pull request. At work, the controls software group uses Fossil "internally", but the company is still "standardized" on SVN (because the IT group's vision is for "thin client" PCs that are fully interchangeable, which doesn't work for my group because we need specialized tool chains that don't "play well" with IT's vision). We use Fossil for our day-to-day work, only committing releases to SVN. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users