git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, "Taylor Blau" <me@ttaylorr.com>,
	"Junio C Hamano" <gitster@pobox.com>,
	"Christian Couder" <chriscool@tuxfamily.org>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: taking a break from Git
Date: Tue, 21 Dec 2021 00:48:44 +0530	[thread overview]
Message-ID: <b6961967-ce5b-d5ab-d44f-69ee58641837@gmail.com> (raw)
In-Reply-To: <YbohRy22vBuDZsG4@nand.local>

Hi Peff,

On 15/12/21 10:39 pm, Taylor Blau wrote:
> On Wed, Dec 15, 2021 at 11:38:25AM -0500, Jeff King wrote:
>> Hey all,
>>
>> I'm going to be offline and completely absent from the mailing list for
>> five months starting at the end of December. After that, things are up
>> in the air, but I may not be as involved in the project as I have been.
>>
>> Sorry, there's no juicy gossip or drama to share. I still like everyone,
>> and think it's a cool project. ;) After 15 years, it just feels like
>> it's time for a break and to perhaps apply my brain to something else
>> for a while.
> 
> I am going to miss seeing patches and review from you tremendously.
> 
> ...
>
> I am a better programmer and Git contributor directly because of Peff's
> efforts. I am sure that anybody who has been fortunate enough to get
> review or advice from Peff feels the same as I do.
> 

I could resonate with this. I've always seen you as a prolific contributor
who is able to provide valuable feedback to long-timers and newcomers all
the same. Thanks for all that you've done so, Peff!

> 
>>    - I really am going to stop reading the list. Even if you cc me. So
>>      please don't get mad if I don't review your patches, or respond to
>>      bug reports. :)
> 
> Please do ;). Enjoy your well deserved time off, and thank you.
> 

I hope the same too. Wishing you luck on your future endeavour, Peff!

-- 
Sivaraam

PS: I've been wanting to interview you for Git Rev News for
quite some time now. Looks like I've waited too long. Given
the circumstance, I don't wish to bother you with one. But if
you feel like giving an interview, feel free to let me know :-)

  parent reply	other threads:[~2021-12-20 19:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 16:38 taking a break from Git Jeff King
2021-12-15 17:09 ` Taylor Blau
2021-12-16  9:46   ` Christian Couder
2021-12-20 19:18   ` Kaartic Sivaraam [this message]
2021-12-15 18:42 ` Junio C Hamano
2021-12-16 14:26 ` rsbecker
2021-12-17 11:06 ` Phillip Wood
2021-12-20 12:45 ` Ævar Arnfjörð Bjarmason
2021-12-20 13:43   ` Jeff King
2021-12-21 16:02 ` Philip Oakley
2021-12-21 18:23 ` Elijah Newren

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=b6961967-ce5b-d5ab-d44f-69ee58641837@gmail.com \
    --to=kaartic.sivaraam@gmail.com \
    --cc=avarab@gmail.com \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=me@ttaylorr.com \
    --cc=peff@peff.net \
    /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.
Code repositories for project(s) associated with this public 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).