git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Atharva Raykar <raykar.ath@gmail.com>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
	Shourya Shukla <periperidip@gmail.com>
Cc: Christian Couder <christian.couder@gmail.com>,
	avarab@gmail.com, Emily Shaffer <emilyshaffer@google.com>,
	Johannes Schindelin <johannes.schindelin@gmx.de>,
	git@vger.kernel.org
Subject: Re: [GSoC] A small survey + My Git Blog, week 10
Date: Tue, 27 Jul 2021 18:40:42 +0530	[thread overview]
Message-ID: <ad8c8e8a-156e-bb10-0305-91fcd595b732@gmail.com> (raw)
In-Reply-To: <b07fe877-f0ba-9a20-47b2-16c8efaa447c@gmail.com>

On 26/07/21 23:56, Kaartic Sivaraam wrote:
> Hi Atharva and Shourya,
> [...]
>> Thunderbird is more like what I am looking for, which has a convenient
>> GUI with loaded batteries, while still being more configurable than Apple
>> Mail and actually handling threading properly. This is what I
>> currently use,
>> but my laptop is unhappy with it, as it eats up around 40-50% of the CPU
>> usage in the background. It also eats up more battery, almost as much as
>> my browser. This is apparently a bug that’s been unresolved for many
>> years
>> now. Git developers reading this: if you have personal recommendations
>> for something that is easy to use but also lightweight, please do let
>> me know! (and it needs to work on macOS)
> 
> That's bad. After a long time of switching, Thunderbird is what worked for
> me too (after some config tweaks, of course). Evolution was close but it
> had some bugs with the composition window. Otherwise Evolution was good,
> light-weight and is well suited for plain-text emails. But looks like
> it only works for Unix-like distributions[1]. So, its not an option for
> you.
> 
> I don't own a Mac and haven't used one for personal use. So, I don't
> have great recommendations. Anyways, light-weight reminds me of mutt[2].
> But its likely one of the non-GUI clients that might also need a bit of
> configuring.
> 
> In case you could consider alternative solutions for filtering e-mail,
> there's the filtering option of Gmail[3] which could help. You could
> filter emails based on certain criteria and send them to specific
> folders[4] which could help you with managing emails to an extent.
> I heavily rely on this feature to keep my Inbox clutter-free to
> an extent.
> 
> [1]: https://en.wikipedia.org/wiki/Comparison_of_email_clients#General
> 
> [2]: http://www.mutt.org/
> 
> [3]: https://support.google.com/mail/answer/6579?hl=en
> 
> [4]:
> https://www.gtricks.com/gmail/organize-gmail-by-sending-emails-directly-to-a-folder-label/

Thanks for the information. I do use the filtering of Gmail, but I
remember back when I used a non-GUI client I had all sorts issues with
mapping the newly made Gmail directories with folders on my system. I
believe you have to configure one each time, which is fine when you
don't have to do it too, often but I had given up after the third time.

>> I just use a straightforward { editor + MUA + git } stack and go with
>> the flow!
> 
> For me it has mostly been this but with some help from tools. Many
> people have found GitGitGadget[5] useful for sending patches to mailing
> list based workflow from a GitHub PR like interface (Thanks to Dscho!)
> You could've heard of it before but you could give it a try and
> see if it helps improve things for you :-)

I appreciate the utility of GitGitGadget, and I thought I'd end up using
that when contributing, but I found email to be simpler and more
intuitive (at the time, it felt less intimidating to use).

> I've heard there's git send-series[6] which says that it helps
> with managing patch series. I haven't used it myself, though.
> 
> These are some tools that come to mind. I believe others could
> likely provide better insights.
> 
> [5]: https://gitgitgadget.github.io/
> 
> [6]: https://github.com/felipec/git-send-series

Thanks, I'll check these out.


  reply	other threads:[~2021-07-27 13:10 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 [this message]
2021-07-26 19:02 ` Felipe Contreras
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=ad8c8e8a-156e-bb10-0305-91fcd595b732@gmail.com \
    --to=raykar.ath@gmail.com \
    --cc=avarab@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=johannes.schindelin@gmx.de \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=periperidip@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 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 NNTP newsgroup(s).