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 <da...@botton.com> 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 > <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
