From: "Theodore Ts'o" <firstname.lastname@example.org> To: "brian m. carlson" <email@example.com>, Jonathan Nieder <firstname.lastname@example.org>, email@example.com, Raxel Gutierrez <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, Junio C Hamano <email@example.com>, Taylor Blau <firstname.lastname@example.org>, Emily Shaffer <email@example.com> Subject: Re: Pain points in Git's patch flow Date: Mon, 26 Apr 2021 10:24:19 -0400 [thread overview] Message-ID: <YIbNE0Fw2VaZt9ry@mit.edu> (raw) In-Reply-To: <YIYfsMsz0Uz48GaI@camp.crustytoothpaste.net> On Mon, Apr 26, 2021 at 02:04:32AM +0000, brian m. carlson wrote: > In general, I have trouble keeping track of the patch mails I've sent. > I do definitely need to refer to them later, but I don't generally keep > them around on my system since they tend to duplicate my repository, so > I end up needing to find them in my mailbox, which as mentioned, is > slow and error prone. A quick and easy feature request to this (which I have had as well) would be implementing a sendmail.fcc config, which if set, would append any mail messages sent by git send-email to the Unix mbox file specified by sendmail.fcc. Once you have the message id of any patch mail that you've sent... > I have trouble finding all the spots where people have given me review > feedback. I have patch mails and responses to those mails go to a > particular folder, but I still often find that I'm not quite sure if > I've gotten every piece of feedback in a review. Sometimes, > embarrassingly, I don't, and then I have to send another reroll. > Regardless, this makes rerolling a series much slower as I have to comb > my mail multiple times. This becomes pretty easy to solve using existing tooling. For people who like web interfaces: https://lore.kernel.org/r/<message-id> (This works today because firstname.lastname@example.org is archived by the lore.kernel.org public-inbox archive.) Or for those who like CLI's and/or text-based mail readers such as mutt or pine: b4 mbox -o /tmp <message-id> This will dump the full mail thread (given any any message-id in that mail thread) to /tmp/<messaige-id>.mbx in Unix mbox format, again relying on lore.kernel.org. I've found this to be especially handy if I've been cc'ed part-way through a mail thread, or if I was only cc'ed on a single patch and I want to see the full patch series for context. Cheers, - Ted
next prev parent reply other threads:[~2021-04-26 14:24 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-14 6:13 Jonathan Nieder 2021-04-14 7:22 ` Bagas Sanjaya 2021-04-14 8:02 ` Junio C Hamano 2021-04-14 21:42 ` Junio C Hamano 2021-04-15 8:49 ` Denton Liu 2021-04-15 6:06 ` Junio C Hamano 2021-04-15 15:45 ` Son Luong Ngoc 2021-04-19 2:57 ` Eric Wong 2021-04-19 13:35 ` Theodore Ts'o 2021-04-21 10:19 ` Ævar Arnfjörð Bjarmason 2021-04-28 7:21 ` Eric Wong 2021-04-28 7:05 ` Eric Wong 2021-04-15 18:25 ` Atharva Raykar 2021-04-16 19:50 ` Junio C Hamano 2021-04-16 20:25 ` Junio C Hamano 2021-05-02 5:35 ` ZheNing Hu 2021-04-18 8:29 ` Sebastian Schuberth 2021-04-18 20:54 ` Ævar Arnfjörð Bjarmason 2021-04-19 2:58 ` Eric Wong 2021-04-19 5:54 ` Sebastian Schuberth 2021-04-19 6:04 ` Sebastian Schuberth 2021-04-19 8:26 ` Ævar Arnfjörð Bjarmason 2021-04-19 19:23 ` Sebastian Schuberth 2021-04-19 22:34 ` Theodore Ts'o 2021-04-20 6:30 ` Sebastian Schuberth 2021-04-20 16:37 ` Theodore Ts'o 2021-04-30 20:45 ` Felipe Contreras 2021-04-20 10:34 ` Ævar Arnfjörð Bjarmason 2021-04-19 19:36 ` Eric Wong 2021-04-19 19:49 ` Sebastian Schuberth 2021-04-19 22:00 ` Konstantin Ryabitsev 2021-05-08 2:10 ` dwh 2021-04-19 21:49 ` Konstantin Ryabitsev 2021-04-19 23:03 ` Stephen Smith 2021-05-08 2:08 ` dwh 2021-05-08 4:41 ` Bagas Sanjaya 2021-04-30 20:58 ` Felipe Contreras 2021-04-21 4:46 ` Daniel Axtens 2021-04-26 2:04 ` brian m. carlson 2021-04-26 14:24 ` Theodore Ts'o [this message] 2021-04-26 14:36 ` Ævar Arnfjörð Bjarmason 2021-04-28 7:59 ` Eric Wong 2021-04-28 22:44 ` brian m. carlson 2021-04-30 20:16 ` Felipe Contreras 2021-04-30 20:35 ` Felipe Contreras 2021-04-30 21:09 ` Felipe Contreras
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=YIbNE0Fw2VaZt9ry@mit.edu \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Pain points in Git'\''s patch flow' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).