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] Push yields "Error: not authorized to write"

On Thursday, 18. Aug 2016, 14:51:37 +0200, Kees Nuyt wrote: > The user jdoe has been given an initial password on both > repositories. You have to use the password of jdoe on the 'root' > repository for push to succeed. The clone and pull commands > succeed because they are probably allowed to any

Re: [fossil-users] Push yields "Error: not authorized to write"

[Default] On Thu, 18 Aug 2016 12:32:44 +0200, Bertram Scharpf wrote: >On Thursday, 18. Aug 2016, 11:36:03 +0200, Stephan Beal wrote: >> On Thu, Aug 18, 2016 at 11:24 AM, Bertram Scharpf >> wrote: >> >> > as root I say: >> > >> > # fossil

Re: [fossil-users] Push yields "Error: not authorized to write"

On Thursday, 18. Aug 2016, 11:36:03 +0200, Stephan Beal wrote: > On Thu, Aug 18, 2016 at 11:24 AM, Bertram Scharpf > wrote: > > > as root I say: > > > > # fossil init -A jdoe someproject.fossil > > [...] > > # fossil server someproject.fossil > > Listening for

Re: [fossil-users] Push yields "Error: not authorized to write"

On Thu, Aug 18, 2016 at 11:24 AM, Bertram Scharpf wrote: > Hi, > > as root I say: > > # fossil init -A jdoe someproject.fossil > [...] > # fossil server someproject.fossil > Listening for HTTP requests on TCP port 8080 > > Then, in another window as a regular

[fossil-users] Push yields "Error: not authorized to write"

Hi, as root I say: # fossil init -A jdoe someproject.fossil [...] # fossil server someproject.fossil Listening for HTTP requests on TCP port 8080 Then, in another window as a regular user: % fossil clone -A jdoe http://localhost:8080 someproject.fossil [...] % mkdir someproject

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