[fossil-users] applied DVCS for collaborative work - on the fossil project itself, or otherwise

2012-12-12 Thread C. Thomas Stover
I have made some great progress on my continuing quest for fire with Fossil yesterday and today. In this episode, my juggling of over-committed time cycled back around to answering questions about branching and merging in the context of various development models using Fossil. In no way am I asha

Re: [fossil-users] applied DVCS for collaborative work - on the fossil project itself, or otherwise

2012-12-13 Thread Matt Welland
One partial solution available today is to use http://chiselapp.com. Simply use their "clone repo" feature with regular pull. What is missing is a way to register the "fork" with the original project. It would be cool if it was possible to submit the URL of the forked repo to the parent. The parent

Re: [fossil-users] applied DVCS for collaborative work - on the fossil project itself, or otherwise

2012-12-13 Thread James Turner
On Thu, Dec 13, 2012 at 09:27:03AM -0700, Matt Welland wrote: > One partial solution available today is to use http://chiselapp.com. Simply > use their "clone repo" feature with regular pull. What is missing is a way > to register the "fork" with the original project. It would be cool if it > was p

Re: [fossil-users] applied DVCS for collaborative work - on the fossil project itself, or otherwise

2012-12-13 Thread C. Thomas Stover
On Thu, 13 Dec 2012 09:27:03 -0700 Matt Welland wrote: > One partial solution available today is to use http://chiselapp.com. > Simply use their "clone repo" feature with regular pull. What exactly does that do over a regular clone & pull? -- www.thomasstover.com _

Re: [fossil-users] applied DVCS for collaborative work - on the fossil project itself, or otherwise

2012-12-13 Thread Matt Welland
On Thu, Dec 13, 2012 at 11:37 AM, C. Thomas Stover wrote: > On Thu, 13 Dec 2012 09:27:03 -0700 > Matt Welland wrote: > > > One partial solution available today is to use http://chiselapp.com. > > Simply use their "clone repo" feature with regular pull. > > What exactly does that do over a regular