git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
	Christian Couder <chriscool@tuxfamily.org>,
	Taylor Blau <me@ttaylorr.com>
Subject: Re: taking a break from Git
Date: Mon, 20 Dec 2021 13:45:05 +0100	[thread overview]
Message-ID: <211220.867dbzwhln.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <YboaAe4LWySOoAe7@coredump.intra.peff.net>


On Wed, Dec 15 2021, Jeff King wrote:

Thanks a lot for everything. Your contributions, advice and example have
been invaluable.

I wish you all the best. I hope this isn't goodbye as far as interaction
with this project is concerned.

>   - 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. :)

A couple of practical questions:

Do you have a preference either way for being kept or omitted from CC?
I.e. if/when you'd come back to have that E-Mail backlog, or for us to
stop CC-ing you? Clearly you'd still get some traffic, but at least us
list regulars could take that into account.

You have various WIP code in topics at https://github.com/peff/git. Some
of which has your SOB, some not. I keep it as a remote and sometimes run
into prior art with "log --all <path>" and the like.

You noted a while ago (IIRC, haven't dug up where) that inline patches
of yours to the list could be assumed to have your SOB, does the same
apply to what's sitting in that repo?

I picked up/stole some patches from it recently for the e48a623dea0
(Merge branch 'ab/http-drop-old-curl', 2021-08-24) topic. It might be
useful for me/others to similarly pick WIP work from there in the
future, obviously while clearly communicating that this is based on some
WIP patch that sat in your repo, not something you submitted on-list.


  parent reply	other threads:[~2021-12-20 13:06 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
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 [this message]
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=211220.867dbzwhln.gmgdl@evledraar.gmail.com \
    --to=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).