Re: [fossil-users] feature implemented or suggestion for stash

On 4/14/2016 11:10 AM, Stephan Beal wrote: On Thu, Apr 14, 2016 at 7:00 PM, Warren Young > wrote: On Apr 12, 2016, at 11:30 PM, Stephan Beal > wrote: > i haven't ever bisected. Wow…

Re: [fossil-users] feature implemented or suggestion for stash

On Thu, Apr 14, 2016 at 7:00 PM, Warren Young wrote: > On Apr 12, 2016, at 11:30 PM, Stephan Beal wrote: > > > > i haven't ever bisected. > > Wow… > > I don’t bisect every day, but when I do bisect, I bisect with Fossil. :) > i've just been lucky -

Re: [fossil-users] feature implemented or suggestion for stash

On 4/14/16, Warren Young wrote: > > I suppose if you’re working on software with 100% regression test coverage, > such problems would never become buried in the project history: as soon as a > change breaks things, you get told about it by the test harness. Not so. The better

Re: [fossil-users] feature implemented or suggestion for stash

On Apr 12, 2016, at 11:30 PM, Stephan Beal wrote: > > i haven't ever bisected. Wow… I don’t bisect every day, but when I do bisect, I bisect with Fossil. :) Bisecting is most useful when you get a bug report from the field and can’t see from that report how any of the

Re: [fossil-users] feature implemented or suggestion for stash

On Tue, Apr 12, 2016 at 8:01 PM, fran wrote: > Bug fixing sometimes involves unplanned commits with nonsense because > of the hurry. > The flow is fast and crude changesets (the stash, right?). i disagree: branches are for that purpose. The stash is not. > Much of

Re: [fossil-users] feature implemented or suggestion for stash

I tried to be the more accurate I can given I am not english spoken to expose what I wanted to say in the first place. Excuse me for the extension of this but I think there is an interesting point here and a patch --- Bug fixing sometimes

Re: [fossil-users] feature implemented or suggestion for stash

Thus said Stephan Beal on Mon, 11 Apr 2016 17:20:22 +0200: > If i understand correctly, that's what fossil intends branches to be > used for. stashes are generally not intended for long-term storage. > They're intended primarily for "oops, i need to quickly do something > over in this

Re: [fossil-users] feature implemented or suggestion for stash

all my samples include messages. If that's the point then I could add all the 'interface' I need into the -m flag including console codes to draw boxes and stuff. 2016-04-11 13:15 GMT-03:00 Stephan Beal : > On Mon, Apr 11, 2016 at 5:56 PM, fran

Re: [fossil-users] feature implemented or suggestion for stash

forget the command line cases. The checkout was a children of the checkout I was requesting to purge. 2016-04-11 13:45 GMT-03:00 fran : > Whats the effect if I use the --integrate option? > > 2016-04-11 13:17 GMT-03:00 Tony Papadimitriou : > >> Once you’re

Re: [fossil-users] feature implemented or suggestion for stash

Whats the effect if I use the --integrate option? 2016-04-11 13:17 GMT-03:00 Tony Papadimitriou : > Once you’re ready to move the changes to a normal branch you simply merge > (but without the –integrate option or else the purge won’t work correctly), > and then purge the private

Re: [fossil-users] feature implemented or suggestion for stash

I don’t know if this will be of any help, but I moved away from using stash altogether for pretty much the same reasons you mention, plus one very important one for me that I don’t like about the stash: the content of the stash only stays on the current PC while I wanted it to follow the repo

Re: [fossil-users] feature implemented or suggestion for stash

On Mon, Apr 11, 2016 at 5:56 PM, fran wrote: > The current listing displays > 1: [199b53d1d70361] on 2016-03-25 05:08:21 > > To the new user this says "something 199b53d1d70361 got 'commited' on such > date"... > Have you tried using the -m option? [stephan@host:~]$

Re: [fossil-users] feature implemented or suggestion for stash

On Mon, Apr 11, 2016 at 4:28 PM, fran wrote: > I never realized the presented uuid was actually the baseline. > Stephan Beal said he wasn't even aware of the 'stash goto' > command! And I (noob user) couldn't understand what > the 'goto' would do. > There are _lots_ of

[fossil-users] feature implemented or suggestion for stash

the stash could give more info about the baseline checkout. It currently shows just the checkout uuid. I never realized the presented uuid was actually the baseline. Stephan Beal said he wasn't even aware of the 'stash goto' command! And I (noob user) couldn't understand what the 'goto' would do.