{"thread":{"id":"53552","subject":"Draft of Git Rev News edition 63","startedAt":"2020-05-26T17:10:48Z","lastAt":"2020-05-27T21:54:43Z","messageCount":3,"participants":["Christian Couder","Damien Robert"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"398587","messageId":"CAP8UFD3MvaAPMUwc=hW-bayDbNpxSX3jtMiPQro4b2Ai17GkNg@mail.gmail.com","threadId":"53552","inReplyTo":null,"subject":"Draft of Git Rev News edition 63","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2020-05-26T17:10:32Z","receivedAt":"2020-05-26T17:10:48Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi everyone!\n\nA draft of a new Git Rev News edition is available here:\n\n  https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-63.md\n\nEveryone is welcome to contribute in any section either by editing the\nabove page on GitHub and sending a pull request, or by commenting on\nthis GitHub issue:\n\n  https://github.com/git/git.github.io/issues/430\n\nYou can also reply to this email.\n\nIn general all kinds of contribution, for example proofreading,\nsuggestions for articles or links, help on the issues in GitHub, and\nso on, are very much appreciated.\n\nI tried to cc everyone who appears in this edition, but maybe I missed\nsome people, sorry about that.\n\nJakub, Markus, Kaartic and me plan to publish this edition on Thursday\nMay 28th in the evening.\n\nThanks,\nChristian.\n"},{"id":"398695","messageId":"20200527211140.qbgbbitoxr4mx7gk@feanor","threadId":"53552","inReplyTo":"CAP8UFD3MvaAPMUwc=hW-bayDbNpxSX3jtMiPQro4b2Ai17GkNg@mail.gmail.com","subject":"Re: Draft of Git Rev News edition 63","fromName":"Damien Robert","fromEmail":"damien.olivier.robert@gmail.com","sentAt":"2020-05-27T21:11:40Z","receivedAt":"2020-05-27T21:11:47Z","isPatch":false,"sender":{"key":"damien.olivier.robert@gmail.com","avatar":null},"body":"From Christian Couder, Tue 26 May 2020 at 19:10:32 (+0200) :\n> A draft of a new Git Rev News edition is available here:\n>   https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-63.md\n\n> # Reviews\n> remote.c: fix handling of push:remote_ref\n\nWow! I don't know who was motivated enough to go through the history of this\nseries, but I am impressed. I just sent a pull request with some\nsuggestions.\n\nThis series was a complete mess, a lesson learned is that I should stay\nfocused on the original scope of the series, rather than try to extend it\nmid-way when I find other bugs in adjacent areas. And instead fix the new\nuncovered bugs in other series.\n\n> This led to some release confusion as Junio then had merged the 2 patches to the next branch, while Damien had sent a version 8 that contains only his patch without the triangular workflow fixes and test cases.\n\n> This last version is now merged in the pu branch, and will is likely to find its way to master, while hopefully the fixes related to triangular workflows will be re-sent separately.\n\nIn \"What's cooking in git\", the series is marked as stalled, so I think Junio\nis waiting for a reroll. I haven't forgotten about this series, but with\nthe current situation I did not have time to rework on it.\n\nMeanwhile, the version v8 in 'pu' does not detect triangular workflows (since\nI ejected that patch).\n\nThe version v6 in 'next' does, but there it has the corner case of\na branch 'foo' which has a pushRemote=foobar but no remote and 'origin'\ndoes not exists. In this case %(push:remote_ref) detects a triangular\nworkflow but `git push` does not.\n\nSo this is really a minor corner case (and I actually think its `git push` which\nshould be fixed here), so it is not too bad that this version is\nin 'next', especially since there are still other bugs in the ref-filter\nmachinery anyway\n(see eg\nhttps://public-inbox.org/git/20200418173651.djzriazxj5kbo6ax@doriath/ and\nhttps://public-inbox.org/git/20200416152145.wp2zeibxmuyas6y6@feanor/).\n\nBest regards,\nDamien\n"},{"id":"398700","messageId":"CAP8UFD1t8e+7_fMPhAFFBQSZ3G1Xxvw+=+mwfX4LB4uKJZek6A@mail.gmail.com","threadId":"53552","inReplyTo":"20200527211140.qbgbbitoxr4mx7gk@feanor","subject":"Re: Draft of Git Rev News edition 63","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2020-05-27T21:54:27Z","receivedAt":"2020-05-27T21:54:43Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Wed, May 27, 2020 at 11:11 PM Damien Robert\n<damien.olivier.robert@gmail.com> wrote:\n>\n> From Christian Couder, Tue 26 May 2020 at 19:10:32 (+0200) :\n> > A draft of a new Git Rev News edition is available here:\n> >   https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-63.md\n>\n> > # Reviews\n> > remote.c: fix handling of push:remote_ref\n>\n> Wow! I don't know who was motivated enough to go through the history of this\n> series, but I am impressed. I just sent a pull request with some\n> suggestions.\n\nThanks! I merged your pull request and then reformatted the result a bit.\n\n> This series was a complete mess, a lesson learned is that I should stay\n> focused on the original scope of the series, rather than try to extend it\n> mid-way when I find other bugs in adjacent areas. And instead fix the new\n> uncovered bugs in other series.\n\nYeah, I hope that this lesson can be learned by others reading the article.\n\n> In \"What's cooking in git\", the series is marked as stalled, so I think Junio\n> is waiting for a reroll. I haven't forgotten about this series, but with\n> the current situation I did not have time to rework on it.\n\nYeah, no worries about that. It's ok to take your time.\n\n> Meanwhile, the version v8 in 'pu' does not detect triangular workflows (since\n> I ejected that patch).\n>\n> The version v6 in 'next' does, but there it has the corner case of\n> a branch 'foo' which has a pushRemote=foobar but no remote and 'origin'\n> does not exists. In this case %(push:remote_ref) detects a triangular\n> workflow but `git push` does not.\n>\n> So this is really a minor corner case (and I actually think its `git push` which\n> should be fixed here), so it is not too bad that this version is\n> in 'next', especially since there are still other bugs in the ref-filter\n> machinery anyway\n> (see eg\n> https://public-inbox.org/git/20200418173651.djzriazxj5kbo6ax@doriath/ and\n> https://public-inbox.org/git/20200416152145.wp2zeibxmuyas6y6@feanor/).\n\nYeah, I think both versions v6 and v8 are already significant\nimprovements over the current situation.\n\nThanks,\nChristian.\n"}]}