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

Re: [Outreachy][PATCH] promisor-remote: honor promisor.fetchOrder when trying remotes

From
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Date
Nov 13, 2026, 09:51 UTC
Message-ID
<a3ae6756-0985-4873-9d23-96d4bb49eda5@gmail.com>
In-Reply-To
<CAG7jffxRscX3ntX3p8L1GwGbs7WJmj6WoKPRGUuz3wcCS0NZag@mail.gmail.com>
On 11/6/26 04:25, Tatchou Yopa Nelly wrote:
> Hi Tanga,
>
Next time try to make sure the person you are writing to is in the To/Cc fields as appropriate. Otherwise, there is a chance that they will not even receive your message since not everyone reads the list by subscribing to it.> Kaartic, I've also re-read SubmittingPatches#describe-changes and
> rewritten the commit message to describe the change rather than
> address the reviewers directly.
That is good!
Show 6 quoted lines
> On the RFC point: I treated the
> Phase 2 config work as the micro-patch and skipped the RFC step
> you pointed out. Should I step back and send the design RFC first,
> or keep the current patch as a prototype while we discuss the
> config shape on the list?
> I think treating the current patch as a RFC patch and discussing the shape is a good idea. The only concern I have is that this patch is submitted in the context of Outreachy and the candidate that we may potentially pick will work[note 1] on this during their Outreachy internship period. So, discussing this now sounds a little premature to me
Of course, I don't mean to suggest that no two people should work on related areas. I'm just thinking it might be ideal to avoid premature work among Outreachy contributors before even the Outreachy selections are out.
[note 1]: During the candidate discussion, it may also happen that we may not pick a candidate for the project. It is totally fine to work on this in that case as there will be no conflicts. But none of this is clear now, TBH.
-- 
Sivaraam
Previous: Tatchou Yopa NellyNext: Tatchou Yopa Nelly
Message 5 of 11 in “promisor-remote: honor promisor.fetchOrder when trying remotes”
  1. Yopa NellyNov 4, 2026
  2. Tanga JorisNov 5, 2026
  3. Kaartic SivaraamNov 5, 2026
  4. Tatchou Yopa NellyNov 5, 2026
  5. Kaartic SivaraamNov 13, 2026
  6. Tatchou Yopa NellyNov 13, 2026
  7. [Outreachy][PATCH v2] promisor-remote: honor promisor.fetchOrder when trying remotesYopa Nelly, Nov 5, 2026
  8. Junio C HamanoNov 5, 2026
  9. Christian CouderNov 13, 2026
  10. Tatchou Yopa NellyNov 13, 2026
  11. Junio C HamanoNov 13, 2026

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.