> Le 6 août 2022 à 14:31, Développement - Sowebio a
> écrit :
>
> Hi Pascal,
>> Thus I've created a mirror repository on Github:
>>
>> https://github.com/Blady-Com/gnoga
> For tickets, should we focus on Gihub on stay on SourceForge ?
Hi Stéphane,
Until I'll be able to set all Alire stuff,
> Le 7 avr. 2022 à 22:01, Blady via Gnoga-list
> a écrit :
>
> Thanks a lot for all your answers.
>
> Thus I tried to set master for d) which got the majority.
>
> But SF GIT is enough twisted to reject the simple command:
>
> % git push --force origin master
> Total 0 (delta 0), reused 0
Thanks a lot for all your answers.
Thus I tried to set master for d) which got the majority.
But SF GIT is enough twisted to reject the simple command:
% git push --force origin master
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
remote: error: denying non-fast-forward refs/heads/master
I vote d. That was how it was originally and what I think most expect.
On Sun, Mar 20, 2022 at 7:16 AM Blady via Gnoga-list <
gnoga-list@lists.sourceforge.net> wrote:
> Hello,
>
> The master branch of the Gnoga GIT repo is stuck on version 1.2a for many
> years.
> Some users point out that, for
Hi Pascal
I vote (d) for the reasons expressed by Rolf.
d) too cause this is the (informal) standard... i.e. the way most
people understand that.
--
Stéphane Rivière
Ile d'Oléron - France
OpenPGP_0x68A4C5C1D498F92F.asc
Description: OpenPGP public key
OpenPGP_signature
Description:
Hello Pascal,
I vote (d) for the reasons expressed by Rolf.
Cheers,
Gautier
*From:* Blady
*Sent:* Dimanche, Mars 20, 2022 12:15PM
*To:* Gnoga-List
*Cc:* David Botton , Jeffrey R. Carter
, David Botton , Gdemont
> 21 mars 2022 kl. 11:09 skrev Jean-Pierre Rosen :
>
> I concur, with the suggestion to add a "stable" branch corresponding to a).
> Of course, this branch would be moved up as new stable releases appear.
I would find it more natural if ’stable’ points to the latest stable - in this
case
I concur, with the suggestion to add a "stable" branch corresponding to a).
Of course, this branch would be moved up as new stable releases appear.
Le 21/03/2022 à 10:31, Rolf Ebert GCC a écrit :
I had the very same problem when I first tried Gnoga. I simply checked
out the master branch
I had the very same problem when I first tried Gnoga. I simply checked
out the master branch expecting the latest development.
I therefore vote for (d). Having the incompatibilities from
internationalisation we can also call the latest V1 commit the stable
branch. Master doesn't necessarily mean
Hello,
if the last stable version is V2, there is no reason to set the
master as V1.
The rule must be to set the master on the last stable version, as usual.
So my preference is for c) option with 2.1a.
Thanks
Marc
Le 20/03/2022 à 12:15, Blady via Gnoga-list a écrit :
Hello,
The master
Hello,
The master branch of the Gnoga GIT repo is stuck on version 1.2a for many years.
Some users point out that, for instance:
"It is customary when using git to have the master branch point at the latest
stable branch. Is there any reason not to for gnoga?" (from Tama)
Thus I propose some
11 matches
Mail list logo
