{"thread":{"id":"60040","subject":"Draft of Git Rev News edition 101","startedAt":"2023-07-29T20:38:41Z","lastAt":"2023-07-31T17:52:12Z","messageCount":4,"participants":["Christian Couder","Kristoffer Haugsbakk","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"479981","messageId":"CAP8UFD1M3sRPEJ42v2=pQ_CQYY+PN64Swx70O7D_=VfbhSwKLg@mail.gmail.com","threadId":"60040","inReplyTo":null,"subject":"Draft of Git Rev News edition 101","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2023-07-29T20:37:55Z","receivedAt":"2023-07-29T20:38:41Z","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-101.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/652\n\nYou can also reply to this email.\n\nIn general all kinds of contributions, for example proofreading,\nsuggestions for articles or links, help on the issues in GitHub,\nvolunteering for being interviewed and so on, are very much\nappreciated.\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 I plan to publish this edition late on\nMonday July 31th.\n\nThanks,\nChristian.\n"},{"id":"479988","messageId":"a5c359d6-6c21-489c-a4a3-a21219ab727a@app.fastmail.com","threadId":"60040","inReplyTo":"CAP8UFD1M3sRPEJ42v2=pQ_CQYY+PN64Swx70O7D_=VfbhSwKLg@mail.gmail.com","subject":"Re: Draft of Git Rev News edition 101","fromName":"Kristoffer Haugsbakk","fromEmail":"code@khaugsbakk.name","sentAt":"2023-07-31T10:10:41Z","receivedAt":"2023-07-31T10:11:45Z","isPatch":false,"sender":{"key":"code@khaugsbakk.name","avatar":"https://avatars.githubusercontent.com/u/2229597?v=4"},"body":"> The Magic of Empty Git Commit by Pradumna Saraf on DEV.to - a simple\n> description on how to create an empty commit, and why one would might\n> want one.\n\nThe article does a poor job of motivating empty commits in my opinion.\n\n> > Although seemingly counterintuitive, [empty commits] offer valuable\n> benefits for documentation, triggering automation.\n> […]\n> Empty commits might seem unusual, but they offer significant advantages\n> in managing version control. By documenting milestones, triggering\n> automation processes, and maintaining codebase stability, empty commits\n> can improve collaboration and project management.\n\nSo one use-case that is clear from the above is as a hack for triggering\nbuilds or something that require a new commit (in other words: that can’t\nsimply be rerun). The rest—documenting milestones, maintaining codebase\nstability—is not obvious since you usually do that in a regular commit.\n\nYou can see from the comments that other people also don’t understand what\nthe motivation is.\n\nI use empty commits myself because I’ve seen use-cases for it described on\nthis list. For example: storing the cover letter as the first (empty)\ncommit on the branch. Definitely useful for in-progress work.\n\nThe article, in contrast, just asserts that it is useful and then provides\na one-liner as its technical content.\n\nMy opinion from the peanut gallery is that the article isn’t worth the\ninclusion.\n\n-- \nKristoffer Haugsbakk\n"},{"id":"480004","messageId":"CAP8UFD0VJJ1b29W6VOmy+XR4Bi+gJeL1k7cb0a=cHkyp7O4Nsg@mail.gmail.com","threadId":"60040","inReplyTo":"a5c359d6-6c21-489c-a4a3-a21219ab727a@app.fastmail.com","subject":"Re: Draft of Git Rev News edition 101","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2023-07-31T17:14:25Z","receivedAt":"2023-07-31T17:17:03Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Mon, Jul 31, 2023 at 12:11 PM Kristoffer Haugsbakk\n<code@khaugsbakk.name> wrote:\n>\n> > The Magic of Empty Git Commit by Pradumna Saraf on DEV.to - a simple\n> > description on how to create an empty commit, and why one would might\n> > want one.\n>\n> The article does a poor job of motivating empty commits in my opinion.\n\n...\n\n> My opinion from the peanut gallery is that the article isn’t worth the\n> inclusion.\n\nThanks for your opinion!\n\nJakub what do you think about it?\n"},{"id":"480006","messageId":"CAPc5daXep8yDGERqEZFPxvh_rQipLk47YPwMV0BV+8SBBwU=Ug@mail.gmail.com","threadId":"60040","inReplyTo":"CAP8UFD0VJJ1b29W6VOmy+XR4Bi+gJeL1k7cb0a=cHkyp7O4Nsg@mail.gmail.com","subject":"Re: Draft of Git Rev News edition 101","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2023-07-31T17:51:55Z","receivedAt":"2023-07-31T17:52:12Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"The particular article may offer little new things, but I suspect\nother articles in the same list are also rehashes of what has already\nbeen covered elsewhere, so it does not look particularly bad from that\npoint of view. I have nothing against its inclusion or removal from\nthe list, but I hope the author of the article does not take offence\n(this is the risk of working on drafts in the public).\n\nOn Mon, Jul 31, 2023 at 10:14 AM Christian Couder\n<christian.couder@gmail.com> wrote:\n>\n> On Mon, Jul 31, 2023 at 12:11 PM Kristoffer Haugsbakk\n> <code@khaugsbakk.name> wrote:\n> >\n> > > The Magic of Empty Git Commit by Pradumna Saraf on DEV.to - a simple\n> > > description on how to create an empty commit, and why one would might\n> > > want one.\n> >\n> > The article does a poor job of motivating empty commits in my opinion.\n>\n> ...\n>\n> > My opinion from the peanut gallery is that the article isn’t worth the\n> > inclusion.\n>\n> Thanks for your opinion!\n>\n> Jakub what do you think about it?\n"}]}