Re: [fossil-users] Noob usage questions

On Fri, Apr 22, 2016 at 9:03 PM, Steve Schow wrote: > > Right well I’m just trying to figure out a way to automate thing so the > dev never has to worry about copy and pasting any kind of ticket or checkin > numbers from one place to another. I want it to just happen

Re: [fossil-users] Noob usage questions

On Apr 22, 2016, at 10:35 PM, Ron W wrote: > > At work, my team keeps autosync on. We do all our code changes in branches. > Our workflow is: > 1. An issue ticket is created, describing either a problem or a specification. > 2. (wait until issue is reviewed and approved) >

Re: [fossil-users] Noob usage questions

On Fri, Apr 22, 2016 at 8:33 PM, Steve Schow wrote: > > > the question about auto-sync is only an open ended question. There could > be some work flows that may work with or without it as far as i can tell, > but i’m just asking about what others might be doing.. > > with

Re: [fossil-users] Noob usage questions

Hi Richard, On 22 April 2016 07:07PM, Richard Hipp wrote: > On 4/22/16, Steve Schow wrote: > > 2 - I notice fossil doesn’t endorse or seem to directly support the > > squashing of commits. > > Right. The Fossil philosophy is different from Git. In Fossil, we > work hard to

Re: [fossil-users] Noob usage questions

Beautiful explanation! Thank you! The dot clicking functionality is really very cool, that actually makes everything way easy to deal with, as far as code review…especially with the background color stuff in there. The Webgui is starting to make more sense to me as I look at these examples.

Re: [fossil-users] Noob usage questions

On 4/22/16, Steve Schow wrote: > > Im not sure if you’re saying a merge here would > merge multiple commits from one branch into a single commit on the dest > branch? You said it preserves the history, but that would infer that the > merge would not squash the commits in the

Re: [fossil-users] Noob usage questions

On Apr 22, 2016, at 5:07 PM, Richard Hipp wrote: > If you want see a sequence of changes as a single diff, bring up a > timeline that shows all the changes, click on the "node" of the > origin, then click on the last check-in, then it will show you a diff > between those two

Re: [fossil-users] Noob usage questions

On Apr 22, 2016, at 5:07 PM, Richard Hipp wrote: > On 4/22/16, Steve Schow wrote: >> >> 1 - I notice tickets numbers are not automatically cross linked with >> commits. > > Links are automatic if you include the ticket number [nn] > somewhere in the

Re: [fossil-users] Noob usage questions

On 22 Apr 15:38, Steve Schow wrote: > 3 - whether to use auto-sync or not. I think you are making things overly complicated in question 3. If I understand properly, you want one trusted person to approve code before it gets into trunk on the main repository. Here is a policy that could accomplish

Re: [fossil-users] Noob usage questions

On 4/22/16, Steve Schow wrote: > > 1 - I notice tickets numbers are not automatically cross linked with > commits. Links are automatic if you include the ticket number [nn] somewhere in the check-in comment. See the check-in at

[fossil-users] Noob usage questions

I have just discovered fossil and I am kind of blown away by all it can do! I love how simple this is to install and administrate for small projects. The other competing products like GitLab or Phabricator, etc, are orders of magnitude too complicated for small projects that just need some