From: Eric Wong <email@example.com> To: "brian m. carlson" <firstname.lastname@example.org>, Jonathan Nieder <email@example.com>, firstname.lastname@example.org, Raxel Gutierrez <email@example.com>, firstname.lastname@example.org, email@example.com, Junio C Hamano <firstname.lastname@example.org>, Taylor Blau <email@example.com>, Emily Shaffer <firstname.lastname@example.org> Subject: Re: Pain points in Git's patch flow Date: Wed, 28 Apr 2021 07:59:27 +0000 [thread overview] Message-ID: <20210428075927.GC13114@dcvr> (raw) In-Reply-To: <YIYfsMsz0Uz48GaI@camp.crustytoothpaste.net> "brian m. carlson" <email@example.com> wrote: > I have tooling to automatically generate the proper range for > range-diffs in cover letters, but that tooling requires some sort of > manual timestamp, which means I need to go search for my previous series > to find the date and generate the range diff, or if I'm in a rush, I > just have to omit it. This can take some time, having to guess what I > named the cover letter the last time and search for it in a mailbox with > a 6-digit quantity of mails. > > 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. Along the lines of what Ted said about Fcc, I've always Bcc-ed myself on every message I send to verify deliverability and check/train my spam filter. What search tool do you use? mairix can handle the 6-digit quantity of the git list fairly well. The following finds all threads with "sandals" in From/To/Cc: mairix -t a:sandals d:YYYYMMDD-YYYYMMDD and dumps it to whatever Maildir/mbox/IMAP "mfolder" you've configured. (prefixes in public-inbox such as "a:", "d:" and "s:" are stolen from mairix; though mairix ranges use "-" and public-inbox uses ".." due to Xapian). I've also heard good things about notmuch, but I archive old mail to gzipped mboxrd right now, and that only supports Maildir... I learned to use Xapian by reading code in notmuch.  Fwiw, I'm also working on an AGPL Perl5 storage+search CLI that scales to 7/8-digit mail collections. It's not ready for prime-time, yet, but getting there... (Assuming it doesn't set my SSD on fire, first :x)
next prev parent reply other threads:[~2021-04-28 7:59 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 2021-04-26 14:36 ` Ævar Arnfjörð Bjarmason 2021-04-28 7:59 ` Eric Wong [this message] 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=20210428075927.GC13114@dcvr \ --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 \ --email@example.com \ --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).