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

Re: [PATCH 2/2] transport-helper: update remote helper namespace

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 14, 2013, 18:45 UTC
Message-ID
<7vobdh54uh.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAMP44s22N9_E4oBG0UztXE0yAkX8TmQaE9-x1_wDHqv3bvZ0EQ@mail.gmail.com>
Felipe Contreras <felipe.contreras@gmail.com> writes:
Show 25 quoted lines
> On Sun, Apr 14, 2013 at 12:13 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> Felipe Contreras <felipe.contreras@gmail.com> writes:
>>
>>> Why wasn't this patch merged to 'pu'? To my knowledge nobody raised
>>> any real concerns.
>>
>> There are many reasons not to queue _everything_ ever posted to the
>> list on 'pu', and they are almost always not a deliberate rejection.
>>
>> The maintainer may have thought he is not the best person to judge
>> changes to the area the patch touches, and may be expecting further
>> comments from others, but haven't said "Comments?" and waiting for
>> them to say something without being asked. Or the maintainer may
>> have judged that it is likely to result in wasted work if he queues
>> that version of the patch, fixing trivial nits himself, only to see
>> a reroll arrive before the day's integration cycle finishes (which
>> makes him run the cycle again). Or the maintainer may have been busy
>> tending to other topics. Or the maintainer may have pushed the patch
>> down the queue for any of the above reasons to deal with it later,
>> and after having tended to others' topics, may have forgotten about
>> that patch.
>
> The world is full of possibilities, but most of them are irrelevant,
> specially since 'the maintainer' is right here and can mention the
> reason himself. Is there anything wrong in asking?

An earlier draft of my message starte with "Do you have to be combative to ask a simple 'did you forget this?' question?", but later I removed it. That was what made it irrelevant ;-)

Just rerolling with what _you_ think is an appropriate level of explanation (either or both in log and in-code) and see what happens would probably be the best way to proceed, I think, at this point. Either you hear "It still is wrong and too sketchy", "Yeah, thinking about it again, this is sufficient" from others. Or a silent, which I am inclined to take as much closer to the latter after all the discussion.

Previous: Felipe ContrerasNext: Jeff King
Message 12 of 14 in “transport-helper: general fixes”
  1. 0/2 transport-helper: general fixesFelipe Contreras, Apr 11, 2013
  2. 1/2 transport-helper: improve push messagesFelipe Contreras, Apr 11, 2013
  3. Jeff KingApr 11, 2013
  4. 2/2 transport-helper: update remote helper namespaceFelipe Contreras, Apr 11, 2013
  5. Jeff KingApr 11, 2013
  6. Felipe ContrerasApr 11, 2013
  7. Jeff KingApr 11, 2013
  8. Felipe ContrerasApr 11, 2013
  9. Felipe ContrerasApr 13, 2013
  10. Junio C HamanoApr 14, 2013
  11. Felipe ContrerasApr 14, 2013
  12. Junio C HamanoApr 14, 2013
  13. Jeff KingApr 14, 2013
  14. Jonathan NiederApr 16, 2013

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.