{"thread":{"id":"66765","subject":"[Outreachy] Config shape for promisor fetch ordering some thoughts","startedAt":"2026-11-04T08:58:13Z","lastAt":"2026-11-04T08:58:13Z","messageCount":1,"participants":["Tatchou Yopa Nelly"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"557412","messageId":"CAG7jffxDguporrsGrB1Wv6K1DPVa4zbRpNjYNn9B1Nytp06RqA@mail.gmail.com","threadId":"66765","inReplyTo":null,"subject":"[Outreachy] Config shape for promisor fetch ordering some thoughts","fromName":"Tatchou Yopa Nelly","fromEmail":"yopatatchou@gmail.com","sentAt":"2026-11-04T08:58:13Z","receivedAt":"2026-11-04T08:58:13Z","isPatch":false,"sender":{"key":"yopatatchou@gmail.com","avatar":null},"body":"Hello everyone,\n\nI'm Yopa Nelly, applying for the promisor remote fetch ordering\nproject with Kaartic Sivaraam. I've been reading through\npromisor-remote.c and t5710 to understand what happens today, and\nbefore I start writing anything I wanted to get some feedback on\nthe config shape. The project page says to float it on the list\nfirst, so here I am.\n\nWhat I think happens now: remotes are kept in a linked list in\nconfig order, and the extensions.partialClone remote gets moved to\nthe end. Then lazy_fetch_objects() goes through the list twice\nonce for the remotes the server told us to use and once for the\nrest. As far as I can tell there's no way for a user to say\n\"actually, try this one first\" other than moving config lines\naround.\n\nSo the two options I keep coming back to:\n\n  1. remote.<name>.promisorPriority = <number>\n  2. promisor.fetchOrder = <comma-separated list>\n\nI think I prefer the list. Numbers feel fine when there's one config\nfile, but once it's spread across system/global/local it gets hard\nto look at and know what the order will be. A list is easier to\nread, and it's easier to override in a later config file without\nhaving to pick a number that beats whatever was there before. It\nalso maps pretty directly onto the linked list we already have, so\nhopefully it's not a huge change to sort it.\n\nThe thing I keep tripping over with the numbers approach is what to\ndo with remotes that don't have a priority set. Zero? Infinity?\nSomething in between? With a list, \"not listed\" means \"after the\nlisted ones, in the usual order,\" which feels obvious.\n\nA few cases I'm not sure about and would love an opinion on:\n\n- If someone names a remote in promisor.fetchOrder that isn't\n  actually a promisor remote, is that an error, a warning, or just\n  ignore it?\n- Does extensions.partialClone still go to the end, or can an\n  explicit entry in the list override that?\n- Do we expect to want different orders depending on which remote\n  we're fetching from later on? If yes, that makes the per-remote\n  number look more appealing.\n\nI'd rather sort this out now than write something and then have to\nredo it. Any preference, or anything I've got wrong about how it\nworks today?\n\nThanks,\nYopa Nelly\nGitHub: https://github.com/YopaNelly\n\n"}]}