Re: [Gnoga-list] GIT master branch discussion.
> 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, I prefer to keep SourceForge as current repository. Regards, Pascal. https://blady.pagesperso-orange.fr ___ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list
Re: [Gnoga-list] GIT master branch discussion.
> 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 (delta 0), pack-reused 0 > remote: error: denying non-fast-forward refs/heads/master (you should pull > first) > To https://git.code.sf.net/p/gnoga/code > ! [remote rejected] master -> master (non-fast-forward) > error: failed to push some refs to 'https://git.code.sf.net/p/gnoga/code' > > I tried more GIT commands without success but I'm not an experienced GIT user. > > Any GIT help will be appreciated. Hello all, Well, I looked SF documentation and found: https://sourceforge.net/p/forge/documentation/Git/#deleting-master-after-changing-default-branch But It seemed to me a bit dangerous and surely beyond by git knowledge. Thus I've created a mirror repository on Github: https://github.com/Blady-Com/gnoga The master is at the top. There are two development branches: dev_1.7 and dev_2.2. There are tags corresponding to stable releases. Feel free to report any discrepancy. Next steps: adding Alire support... Regards, Pascal. https://blady.pagesperso-orange.fr ___ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list
Re: [Gnoga-list] GIT master branch discussion.
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 (you should pull first) To https://git.code.sf.net/p/gnoga/code ! [remote rejected] master -> master (non-fast-forward) error: failed to push some refs to 'https://git.code.sf.net/p/gnoga/code' I tried more GIT commands without success but I'm not an experienced GIT user. Any GIT help will be appreciated. Thanks, Pascal. > Le 27 mars 2022 à 03:16, David Botton a écrit : > > 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 > 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 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 options: > > a) set master to the last stable V1 commit, that is V1.6a > b) set master to the last V1 commit, that is V1.7-alpha > c) set master to the last stable V2 commit, that is V2.1a > d) set master to the last V2 commit, that is V2.2-alpha > e) add branches named edge, stable... > f) do nothing > > My preference is for a). > > What is your feedback? > > Thanks, Pascal. > https://blady.pagesperso-orange.fr ___ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list
Re: [Gnoga-list] GIT master branch discussion.
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 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 options: > > a) set master to the last stable V1 commit, that is V1.6a > b) set master to the last V1 commit, that is V1.7-alpha > c) set master to the last stable V2 commit, that is V2.1a > d) set master to the last V2 commit, that is V2.2-alpha > e) add branches named edge, stable... > f) do nothing > > My preference is for a). > > What is your feedback? > > Thanks, Pascal. > https://blady.pagesperso-orange.fr > > > > > ___ > Gnoga-list mailing list > Gnoga-list@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/gnoga-list > ___ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list
Re: [Gnoga-list] GIT master branch discussion.
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: OpenPGP digital signature ___ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list
Re: [Gnoga-list] GIT master branch discussion.
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 *Subject:* GIT master branch discussion. 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 options: a) set master to the last stable V1 commit, that is V1.6a b) set master to the last V1 commit, that is V1.7-alpha c) set master to the last stable V2 commit, that is V2.1a d) set master to the last V2 commit, that is V2.2-alpha e) add branches named edge, stable... f) do nothing My preference is for a). What is your feedback? Thanks, Pascal. https://blady.pagesperso-orange.fr ___ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list
Re: [Gnoga-list] GIT master branch discussion.
> 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 alternative c. Ie the last stable v2. /Björn Björn Lundin b.f.lun...@gmail.com ___ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list
Re: [Gnoga-list] GIT master branch discussion.
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 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 stable. It means newest in most of the public projects that I know. regards Rolf Am 20.03.2022 um 12:15 schrieb Blady via Gnoga-list: 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 options: a) set master to the last stable V1 commit, that is V1.6a b) set master to the last V1 commit, that is V1.7-alpha c) set master to the last stable V2 commit, that is V2.1a d) set master to the last V2 commit, that is V2.2-alpha e) add branches named edge, stable... f) do nothing My preference is for a). What is your feedback? Thanks, Pascal. https://blady.pagesperso-orange.fr ___ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list ___ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list -- J-P. Rosen Adalog 2 rue du Docteur Lombard, 92441 Issy-les-Moulineaux CEDEX Tel: +33 1 45 29 21 52 https://www.adalog.fr ___ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list
Re: [Gnoga-list] GIT master branch discussion.
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 stable. It means newest in most of the public projects that I know. regards Rolf Am 20.03.2022 um 12:15 schrieb Blady via Gnoga-list: 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 options: a) set master to the last stable V1 commit, that is V1.6a b) set master to the last V1 commit, that is V1.7-alpha c) set master to the last stable V2 commit, that is V2.1a d) set master to the last V2 commit, that is V2.2-alpha e) add branches named edge, stable... f) do nothing My preference is for a). What is your feedback? Thanks, Pascal. https://blady.pagesperso-orange.fr ___ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list ___ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list
Re: [Gnoga-list] GIT master branch discussion.
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 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 options: a) set master to the last stable V1 commit, that is V1.6a b) set master to the last V1 commit, that is V1.7-alpha c) set master to the last stable V2 commit, that is V2.1a d) set master to the last V2 commit, that is V2.2-alpha e) add branches named edge, stable... f) do nothing My preference is for a). What is your feedback? Thanks, Pascal. https://blady.pagesperso-orange.fr ___ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list ___ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list
[Gnoga-list] GIT master branch discussion.
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 options: a) set master to the last stable V1 commit, that is V1.6a b) set master to the last V1 commit, that is V1.7-alpha c) set master to the last stable V2 commit, that is V2.1a d) set master to the last V2 commit, that is V2.2-alpha e) add branches named edge, stable... f) do nothing My preference is for a). What is your feedback? Thanks, Pascal. https://blady.pagesperso-orange.fr ___ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list
