All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Philip Oakley <philipoakley@iee.email>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Philip Oakley via GitGitGadget" <gitgitgadget@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH 2/2] rebase: `preserve` is also a pull option, tell dying users
Date: Wed, 9 Mar 2022 13:18:22 +0100 (CET)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.2203091317220.357@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <fd18d7bf-53b6-50ca-12e7-ac66e8fe75da@iee.email>

Hi Philip,

On Mon, 7 Mar 2022, Philip Oakley wrote:

> On 07/03/2022 16:43, Johannes Schindelin wrote:
> > Hi Philip,
> >
> > On Fri, 4 Mar 2022, Philip Oakley wrote:
> >
> >> I'll have another look at the ways these edge cases could appear, and
> >> try an improve the commit message explanations where the diff doesn't
> >> show sufficient context. It'll be at least next week.
> > Can I punt this patch series back to you? (I sent it upstream on your
> > behalf because I had assumed that you'd want me to, sorry for
> > misunderstanding your intentions.)
> >
> I'm happy to continue to work on this series, and am grateful for your
> support in pushing it through GGG. How is it best to transfer the
> 'ownership' at GGG?

Sadly, I don't know of any way how I could transfer ownership to you, but
maybe you can just open a new one and reference the first thread in the
cover letter?

> I've still got some family issues so it'll be later in the week, or even
> next week before I can update the series.

Sorry to hear that you have issues. These are tough times, and I feel for
you.

Ciao,
Dscho

  reply	other threads:[~2022-03-09 12:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22 10:33 [PATCH 0/2] Update the die() preserve-merges messages to help some users Johannes Schindelin via GitGitGadget
2022-02-22 10:33 ` [PATCH 1/2] rebase: help user when dying with preserve-merges` Philip Oakley via GitGitGadget
2022-02-22 15:32   ` Ævar Arnfjörð Bjarmason
2022-02-22 16:06     ` Philip Oakley
2022-02-23 10:20       ` Ævar Arnfjörð Bjarmason
2022-02-23 17:44         ` Philip Oakley
2022-03-08 13:45           ` Ævar Arnfjörð Bjarmason
2022-02-22 10:33 ` [PATCH 2/2] rebase: `preserve` is also a pull option, tell dying users Philip Oakley via GitGitGadget
2022-02-22 15:34   ` Ævar Arnfjörð Bjarmason
2022-02-22 15:56     ` Philip Oakley
2022-02-22 17:48       ` Philip Oakley
2022-02-23 10:27         ` Ævar Arnfjörð Bjarmason
2022-03-04 14:29           ` Philip Oakley
2022-03-07 16:43             ` Johannes Schindelin
2022-03-07 23:26               ` Philip Oakley
2022-03-09 12:18                 ` Johannes Schindelin [this message]
2022-02-22 18:55 ` [PATCH 0/2] Update the die() preserve-merges messages to help some users Phillip Wood
2022-02-22 20:24   ` Philip Oakley

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=nycvar.QRO.7.76.6.2203091317220.357@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=philipoakley@iee.email \
    /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.