Git Mailing List Archive on
 help / color / Atom feed
From: Vadim Zeitlin <>
Cc: Junio C Hamano <>,
	Johannes Schindelin <>
Subject: Re[2]: [PATCH] fetch: allow running as different users in shared repositories
Date: Sat, 2 May 2020 01:11:36 +0200
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2014 bytes --]

On Thu, 26 Mar 2020 15:40:47 +0100 (CET) Johannes Schindelin <> wrote:

JS> On Thu, 26 Mar 2020, Vadim Zeitlin wrote:
JS> > On Wed, 25 Mar 2020 20:04:09 +0100 Johannes Schindelin wrote:
JS> > JS> That rationale makes sense to me, as does the patch.
JS> >
JS> >  Sorry for a possibly stupid question, but what is the next thing to do
JS> > now? The instructions in Documentation/SubmittingPatches indicate that I
JS> > should wait until the "list forms consensus that [...] your patch is good",
JS> > but it's not quite clear what indicates that a consensus has been reached.
JS> > Is your comment above enough or should I wait for something else? And
JS> > if/when it has been reached, do I really I need to resend the patch to
JS> > the maintainer and cc the list as written in that document? I'm a bit
JS> > surprised by this because I don't see (most) patches being resent to this
JS> > list.
JS> My take is that this was waiting for a review, and I provided it (*not*
JS> asking for any changes), and if there are no further reviews, the patch
JS> should make it into the `pu` branch, then `next` and eventually `master`,
JS> at which point it will be slated for the next official `.0` version.
JS> It might make sense to ask for it to be trickled down into the `maint`
JS> branch, too, in case a `v2.26.1` is released. I would be in favor of that,
JS> but would not do the asking myself ;-)

 Hello again,

 Sorry to nag, but I'd like to return to this patch[*] because it looks
like it could have fallen through the cracks: there didn't seem to be any
more comments about it, except for Johannes' positive review, but it didn't
get mentioned in any "What's cooking" threads since then neither.


 So I'd just like to ask directly, hoping that it's not inappropriate:
Junio, do I need to do anything to get this patch accepted or am I just
being too impatient?

 Thanks in advance,

[-- Attachment #2: Type: APPLICATION/PGP-SIGNATURE, Size: 196 bytes --]

  parent reply index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26  0:44 Vadim Zeitlin
2020-03-26 14:40 ` Johannes Schindelin
2020-03-26 22:32   ` Re[2]: " Vadim Zeitlin
2020-05-01 23:11   ` Vadim Zeitlin [this message]
2020-05-04 16:32     ` Junio C Hamano
2020-05-04 17:04       ` Re[2]: " Vadim Zeitlin
2020-05-04 20:39         ` Junio C Hamano
2020-05-05  0:08           ` Re[2]: " Vadim Zeitlin

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:

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

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Mailing List Archive on

Archives are clonable:
	git clone --mirror git/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 git git/ \
	public-inbox-index git

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone