git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re[2]: [PATCH] fetch: allow running as different users in shared repositories

From
VZVadim Zeitlin <vz-git@zeitlins.org>
Date
May 1, 2020, 23:11 UTC
Message-ID
<E1jUeoi-000205-RT@smtp.tt-solutions.com>
In-Reply-To
<nycvar.QRO.7.76.6.2003261538170.46@tvgsbejvaqbjf.bet>
On Thu, 26 Mar 2020 15:40:47 +0100 (CET) Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

JS> On Thu, 26 Mar 2020, Vadim Zeitlin wrote: JS> 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> 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> 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.
[*] https://public-inbox.org/git/20200319010321.18614-1-vz-git@zeitlins.org/
 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,
VZ
Previous: Vadim ZeitlinNext: Junio C Hamano
Message 4 of 8 in “Re: [PATCH] fetch: allow running as different users in shared repositories”
  1. Vadim ZeitlinMar 26, 2020
  2. Johannes SchindelinMar 26, 2020
  3. Re[2]: [PATCH] fetch: allow running as different users in shared repositoriesVadim Zeitlin, Mar 26, 2020
  4. Re[2]: [PATCH] fetch: allow running as different users in shared repositoriesVadim Zeitlin, May 1, 2020
  5. Junio C HamanoMay 4, 2020
  6. Re[2]: [PATCH] fetch: allow running as different users in shared repositoriesVadim Zeitlin, May 4, 2020
  7. Junio C HamanoMay 4, 2020
  8. Re[2]: [PATCH] fetch: allow running as different users in shared repositoriesVadim Zeitlin, May 5, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.