Re: [fossil-users] Fix for stash-next pointer (fix for the fix)

On Thu, Aug 18, 2016 at 4:03 PM, Warren Young wrote: > > I don’t argue for this to make git users happy, but instead to make Fossil > more like Subversion, where there is no additional step required check out > a new repository. > Technically, Fossil checkouts do work (almost)

Re: [fossil-users] Fix for stash-next pointer (fix for the fix)

On Thu, Aug 18, 2016 at 2:06 PM, Warren Young wrote: > On Aug 17, 2016, at 5:21 PM, Kain Abel wrote: > > > > A former ;) git user would > > lose the stash without asking if he uses close > > You misunderstood my responses above, then. Fossil tells you that

Re: [fossil-users] Fix for stash-next pointer (fix for the fix)

On Aug 17, 2016, at 5:21 PM, Kain Abel wrote: > > A former ;) git user would > lose the stash without asking if he uses close You misunderstood my responses above, then. Fossil tells you that closing the repo will remove the stashes, if any are present, and refuses to

Re: [fossil-users] Fix for stash-next pointer (fix for the fix)

On Aug 18, 2016, at 1:12 AM, Stephan Beal wrote: > > git combines clone/open into a single operation Fossil could as well. If you either don’t give a clone target or that target is a directory instead of a file, it could save the repo file to .fslrepo or similar at the

Re: [fossil-users] Fix for stash-next pointer (fix for the fix)

Dear Stephan, 2016-08-18 9:12 GMT+02:00 Stephan Beal: > i'm guessing that few people ever use 'close'? (i have never - in over 8 > years - used it except when testing fossil.) In my case very rarely and often with 'close --force' and 'open -keep'. With regards, Kain

Re: [fossil-users] Fix for stash-next pointer (fix for the fix)

2016-08-18 9:12 GMT+02:00 Stephan Beal : > On Thu, Aug 18, 2016 at 1:21 AM, Kain Abel wrote: >> >> Git has no open and close, but also stash. > > > git combines clone/open into a single operation, and each clone is tied to a > single open copy, whereas

Re: [fossil-users] Fix for stash-next pointer (fix for the fix)

On Thu, Aug 18, 2016 at 1:21 AM, Kain Abel wrote: > Git has no open and close, but also stash. git combines clone/open into a single operation, and each clone is tied to a single open copy, whereas fossil separates them: one clone can serve multiple local checkouts. The

Re: [fossil-users] Fix for stash-next pointer (fix for the fix)

Just a crude thought: I know, fossil is not git ... but both was designed to preserve informations and to track their changes. (That is a absolute simplification.) Git has no open and close, but also stash. A former ;) git user would lose the stash without asking if he uses close (out of

Re: [fossil-users] Fix for stash-next pointer (fix for the fix)

On 8/17/2016 1:01 PM, Warren Young wrote: It would indeed be nice if Fossil told you up front, as you said. The documentation for --force doesn’t explain this second usage, either. It only talks about “uncommitted changes,” which is not quite the same thing as stashed changes, at

Re: [fossil-users] Fix for stash-next pointer (fix for the fix)

On Aug 17, 2016, at 12:33 PM, Kain Abel wrote: > > Hi Warren, > > 2016-08-17 17:43 GMT+02:00 Warren Young : >> On Aug 16, 2016, at 6:45 AM, Kain Abel wrote: >>> Oh, that surprises me now. This implicit behavior is not explicit >>>

Re: [fossil-users] Fix for stash-next pointer (fix for the fix)

Hi Warren, 2016-08-17 17:43 GMT+02:00 Warren Young : > On Aug 16, 2016, at 6:45 AM, Kain Abel wrote: >> Oh, that surprises me now. This implicit behavior is not explicit >> documented. There is no warning that all stashed changes will be also >> dropped when

Re: [fossil-users] Fix for stash-next pointer (fix for the fix)

On Aug 16, 2016, at 6:45 AM, Kain Abel wrote: > > 2016-08-15 17:58 GMT+02:00 Warren Young : >> >> [...] All stashes go away when you close the repo. > > Oh, that surprises me now. This implicit behavior is not explicit > documented. There is no warning

Re: [fossil-users] Fix for stash-next pointer (fix for the fix)

Hi Warren, 2016-08-15 17:58 GMT+02:00 Warren Young : > > [...] All stashes go away when you close the repo. Oh, that surprises me now. This implicit behavior is not explicit documented. There is no warning that all stashed changes will be also dropped when repository will be

Re: [fossil-users] Fix for stash-next pointer (fix for the fix)

On Aug 15, 2016, at 9:58 AM, Warren Young wrote: > > if your only complaint is that typing long integers is tedious, simply > closing and re-opening the repository in the same directory will reset the > stash counter. All stashes go away when you close the repo. Another

Re: [fossil-users] Fix for stash-next pointer (fix for the fix)

On Aug 14, 2016, at 10:47 AM, Kain Abel wrote: > > 2016-08-13 19:45 GMT+02:00 Richard Hipp : > >> But you still have not made your case for why growth of the stash id >> is a bad thing. > > I know, it would be purely cosmetic. > > What is largest possible

Re: [fossil-users] Fix for stash-next pointer (fix for the fix)

HI, 2016-08-13 19:45 GMT+02:00 Richard Hipp : > But you still have not made your case for why growth of the stash id > is a bad thing. I know, it would be purely cosmetic. What is largest possible stash id on 32 bit systems? My stash ID's after testing are now $ fos pool

Re: [fossil-users] Fix for stash-next pointer (fix for the fix)

On 8/13/16, Kain Abel wrote: > The next try: another version. > > (Prevents the growth from stash id after many push and pop operations.) But you still have not made your case for why growth of the stash id is a bad thing. > > Just for the sake of completeness, > Kain > --

Re: [fossil-users] Fix for stash-next pointer (fix for the fix)

The next try: another version. (Prevents the growth from stash id after many push and pop operations.) Just for the sake of completeness, Kain stash-next_fix_fix.patch Description: Binary data ___ fossil-users mailing list