{"thread":{"id":"58367","subject":"[Proposal] Pass additional metadata to sendemail-validate hook from git send-email","startedAt":"2022-08-26T21:00:32Z","lastAt":"2022-08-29T15:38:07Z","messageCount":3,"participants":["Strawbridge, Michael","brian m. carlson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"462011","messageId":"87czcm7maf.fsf@amd.com","threadId":"58367","inReplyTo":null,"subject":"[Proposal] Pass additional metadata to sendemail-validate hook from git send-email","fromName":"Strawbridge, Michael","fromEmail":"michael.strawbridge@amd.com","sentAt":"2022-08-26T21:00:25Z","receivedAt":"2022-08-26T21:00:32Z","isPatch":false,"sender":{"key":"michael.strawbridge@amd.com","avatar":null},"body":"Hi,\n\nI was hoping to put a feature proposal forward for git send-email.\n\nFor git send-email there is a git hook, sendemail-validate which \ngets the body of the email that will be sent but is missing some \nof the metadata that git send-email has access to.  I propose that \nwe also pass the extra metadata that gets presented to the user \nlater on via stdout such as: From, To, Cc, Subject, Date, \nMessage-Id, X-Mailer, MIME-Version, Content-Transfer-Encoding to \nthe git hook.\n\nI'm willing to work on the patch but want to make sure the idea \nwould be accepted first.\n\nThank you,\nMichael"},{"id":"462046","messageId":"Ywq5J2q9PwBrXnrm@tapette.crustytoothpaste.net","threadId":"58367","inReplyTo":"87czcm7maf.fsf@amd.com","subject":"Re: [Proposal] Pass additional metadata to sendemail-validate hook from git send-emailg","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2022-08-28T00:39:03Z","receivedAt":"2022-08-28T00:39:06Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On 2022-08-26 at 21:00:25, Strawbridge, Michael wrote:\n> Hi,\n\nHey,\n\n> I was hoping to put a feature proposal forward for git send-email.\n> \n> For git send-email there is a git hook, sendemail-validate which\n> gets the body of the email that will be sent but is missing some\n> of the metadata that git send-email has access to.  I propose that\n> we also pass the extra metadata that gets presented to the user\n> later on via stdout such as: From, To, Cc, Subject, Date,\n> Message-Id, X-Mailer, MIME-Version, Content-Transfer-Encoding to\n> the git hook.\n> \n> I'm willing to work on the patch but want to make sure the idea\n> would be accepted first.\n\nI think the idea is interesting and would be willing to see a patch come\nto the list.\n\nHowever, having said that, we typically evaluate patches, not proposals,\nso to see if it's actually accepted, you'd have to actually send a\npatch.  We may find that while the idea is interesting, it turns out to\nbe infeasible, or, for whatever reason, the patch is unsuitable.\n\nI know that this is different from how other projects typically work,\nwhere you typically pitch an idea first and then implement, but it's\nwhat we do here.\n-- \nbrian m. carlson (he/him or they/them)\nToronto, Ontario, CA\n"},{"id":"462095","messageId":"8735dfkqlo.fsf@amd.com","threadId":"58367","inReplyTo":"87czcm7maf.fsf@amd.com","subject":"Re: [Proposal] Pass additional metadata to sendemail-validate hook from git send-email","fromName":"Strawbridge, Michael","fromEmail":"michael.strawbridge@amd.com","sentAt":"2022-08-29T15:37:55Z","receivedAt":"2022-08-29T15:38:07Z","isPatch":false,"sender":{"key":"michael.strawbridge@amd.com","avatar":null},"body":"\nThanks for getting back to me.  I'll write up a patch.\n\nbrian m. carlson writes:\n\n> On 2022-08-26 at 21:00:25, Strawbridge, Michael wrote:\n> > Hi,\n> \n> Hey,\n> \n> > I was hoping to put a feature proposal forward for git \n> > send-email.\n> > \n> > For git send-email there is a git hook, sendemail-validate \n> > which\n> > gets the body of the email that will be sent but is missing \n> > some\n> > of the metadata that git send-email has access to.  I propose \n> > that\n> > we also pass the extra metadata that gets presented to the \n> > user\n> > later on via stdout such as: From, To, Cc, Subject, Date,\n> > Message-Id, X-Mailer, MIME-Version, Content-Transfer-Encoding \n> > to\n> > the git hook.\n> > \n> > I'm willing to work on the patch but want to make sure the \n> > idea\n> > would be accepted first.\n> \n> I think the idea is interesting and would be willing to see a \n> patch come\n> to the list.\n> \n> However, having said that, we typically evaluate patches, not \n> proposals,\n> so to see if it's actually accepted, you'd have to actually send \n> a\n> patch.  We may find that while the idea is interesting, it turns \n> out to\n> be infeasible, or, for whatever reason, the patch is unsuitable.\n> \n> I know that this is different from how other projects typically \n> work,\n> where you typically pitch an idea first and then implement, but \n> it's\n> what we do here.\n> -- \n> brian m. carlson (he/him or they/them)\n> Toronto, Ontario, CA\n"}]}