All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Atharva Raykar <raykar.ath@gmail.com>, git@vger.kernel.org
Cc: Christian Couder <christian.couder@gmail.com>,
	Shourya Shukla <periperidip@gmail.com>,
	Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
	avarab@gmail.com, Emily Shaffer <emilyshaffer@google.com>
Subject: RE: [GSoC] A small survey + My Git Blog, week 10
Date: Mon, 26 Jul 2021 14:02:05 -0500	[thread overview]
Message-ID: <60ff06ad2b298_31bb20891@natae.notmuch> (raw)
In-Reply-To: <90b6bd2d-71e1-b8af-e027-8023f8d4f14c@gmail.com>

Atharva Raykar wrote:
> As for the "survey part", jump to the section here:
> https://atharvaraykar.me/gitnotes/week10#the-mailing-list-developer-workflow
> 
> ...feel free to reply in this thread.

It would have been nice to copy the survey on the email.

> What tools, systems and workflows do you find valuable in your
> day-to-day work? In particular I’d be happy getting insights like:
> 
> * Any strategy or approach to work, kind of like the example I quoted
>   above
> * Any scripts and tools that assist you
> * Opinionated handling of multiple in-flight series and methods to
>   approaching reviews
> * Atharva, you are overthinking this! I just use a straightforward {
>   editor + MUA + git } stack and go with the flow!

Personally I use mbsync + notmuch + notmuch-vim + vim + msmtp. You can
watch an example session in asciinema.org [1].

This deals with the filtering issue that you talked about in your blog
post, for example one of the latest queries I ran is
"from:felipe subject:mergetool", plus there's tags so I can mark
messages with "inbox", "git", or "to-do".

Of course you can use emacs instead of vim, but I use vim.

Haveing all the feedback readily available helps me address it easily.

For me notmuch is like git for mail.

Cheers.

[1] https://asciinema.org/a/oo4yUOQDDF2CrWZbzhZURFtTW

-- 
Felipe Contreras

  parent reply	other threads:[~2021-07-26 19:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-25 12:22 [GSoC] A small survey + My Git Blog, week 10 Atharva Raykar
2021-07-26  8:43 ` Christian Couder
2021-07-26 18:26 ` Kaartic Sivaraam
2021-07-27 13:10   ` Atharva Raykar
2021-07-26 19:02 ` Felipe Contreras [this message]
2021-07-27 13:23   ` Atharva Raykar
2021-07-31 18:29 ` Philippe Blain
2021-08-01  7:06   ` Atharva Raykar

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=60ff06ad2b298_31bb20891@natae.notmuch \
    --to=felipe.contreras@gmail.com \
    --cc=avarab@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=periperidip@gmail.com \
    --cc=raykar.ath@gmail.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.