Re: I have cleaned Leo's branches and updated info issue #1058

2022-03-27 Thread Edward K. Ream
On Sun, Mar 27, 2022 at 1:52 PM Viktor Ransmayr wrote: However now the next important step is the release of Leo 6.6. > Right. All new work will be assigned for the 6.6.1 release, and each issue must have its own PR. Edward -- You received this message because you are subscribed to the Google

Re: I have cleaned Leo's branches and updated info issue #1058

2022-03-27 Thread Viktor Ransmayr
Hello Felix, Am So., 27. März 2022 um 20:11 Uhr schrieb Félix : > Salutations Viktor, > > The felix-server4 branch is specifically where I push development progress > for the 'leoserver.py' file in leo/core. > > Indeed, most of the time it is equal to 'devel', but when I'm working on > new server

Re: I have cleaned Leo's branches and updated info issue #1058

2022-03-27 Thread Félix
Salutations Viktor, The felix-server4 branch is specifically where I push development progress for the 'leoserver.py' file in leo/core. Indeed, most of the time it is equal to 'devel', but when I'm working on new server features, that's the branch where you can see and test those new server f

Re: I have cleaned Leo's branches and updated info issue #1058

2022-03-27 Thread Viktor Ransmayr
Hello Edward & Felix, Am So., 27. März 2022 um 14:19 Uhr schrieb Edward K. Ream < edream...@gmail.com>: > Leo's Github branch page > now contains only > three branches: master, devel and felix-server4. All three branches are > protected. None ca

I have cleaned Leo's branches and updated info issue #1058

2022-03-27 Thread Edward K. Ream
Leo's Github branch page now contains only three branches: master, devel and felix-server4. All three branches are protected. None can be deleted. I have deleted all other branches, including all release branches. Leo's Github release page