{"thread":{"id":"62738","subject":"RE: [PATCH 5/5] remote: announce removal of \"branches/\" and \"remotes/\"","startedAt":"2025-01-04T15:36:13Z","lastAt":"2025-01-06T07:51:16Z","messageCount":2,"participants":["D. Ben Knoble","Patrick Steinhardt"],"isPatch":true,"patchVersion":1,"patchTotal":5},"messages":[{"id":"509912","messageId":"0F4D68EB-27F9-4638-98CD-02515969D677@gmail.com","threadId":"62738","inReplyTo":null,"subject":"RE: [PATCH 5/5] remote: announce removal of \"branches/\" and \"remotes/\"","fromName":"D. Ben Knoble","fromEmail":"ben.knoble@gmail.com","sentAt":"2025-01-04T15:36:10Z","receivedAt":"2025-01-04T15:36:13Z","isPatch":true,"sender":{"key":"ben.knoble@gmail.com","avatar":"https://avatars.githubusercontent.com/u/22802209?v=4"},"body":"> +As our documentation mentions, these directories are not to be found in modern\n> +repositories at all and most users aren't even aware of these mechanisms. They\n> +have been deprecated for almost 20 years and 14 years respectively, and I am\n> +not aware of any reason why anybody would want to use these mechanisms.\n> +Furthermore, the \".git/branches/\" directory is noadays misleadingly named and\n> +may cause confusion as \"branches\" are almost exclusively used in the context of\n> +references.\n\ns/noadays/nowadays\n\nIs the first-person intended? \"I am not aware\" reads like editorial that doesn't\nmatch with the rest of the document (either \"we\" or technical-passive voice).\n\n(PS hopefully my mail client will get this to the right place)\n\n-- \nD. Ben Knoble\n"},{"id":"509953","messageId":"Z3uLLv8DjEicYnNF@pks.im","threadId":"62738","inReplyTo":"0F4D68EB-27F9-4638-98CD-02515969D677@gmail.com","subject":"Re: [PATCH 5/5] remote: announce removal of \"branches/\" and \"remotes/\"","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2025-01-06T07:51:10Z","receivedAt":"2025-01-06T07:51:16Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Sat, Jan 04, 2025 at 10:36:10AM -0500, D. Ben Knoble wrote:\n> > +As our documentation mentions, these directories are not to be found in modern\n> > +repositories at all and most users aren't even aware of these mechanisms. They\n> > +have been deprecated for almost 20 years and 14 years respectively, and I am\n> > +not aware of any reason why anybody would want to use these mechanisms.\n> > +Furthermore, the \".git/branches/\" directory is noadays misleadingly named and\n> > +may cause confusion as \"branches\" are almost exclusively used in the context of\n> > +references.\n> \n> s/noadays/nowadays\n\nThanks, will fix.\n\n> Is the first-person intended? \"I am not aware\" reads like editorial that doesn't\n> match with the rest of the document (either \"we\" or technical-passive voice).\n\nHm. Yes, it was intended initially, mostly because I wanted to stress\nthat this is *my* finding and may not reflect the whole project's\nstance. But while that would've been fine in a commit message, I think\nyou're right and it's less sensible in a committed document. After all,\nthe review process should ensure that the project also agrees with my\nfinding, and at that point it does make sense to say \"we\".\n\n> (PS hopefully my mail client will get this to the right place)\n\nSeems like it did make it to the right place. There is one weirdness\nthough: your mail client sets the \"Reply-To\" header to the message ID of\nthe cover letter somehow, so when replying I don't send it to you but I\ninstead send it to [1].\n\n[1]: 20241211-pks-remote-branches-deprecation-v1-5-1431e2369135@pks.im\n\nPatrick\n"}]}