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

Re: [Outreachy PATCH] checkout: use repository parameter in unique_tracking_name

From
Usman Akinyemi <usmanakinyemi202@gmail.com>
Date
Oct 22, 2026, 09:41 UTC
Message-ID
<CAPSxiM9fCTEoQDv09fX_NZCcLRXYaaCdWXPxDT7JZ+LCwT1YQA@mail.gmail.com>
In-Reply-To
<20261017225326.7827-1-okhuomonajayi54@gmail.com>
>
> The function uses the_repository to read configuration and look up

Which function ? You have left the reader of the commit message to wonder what function ?

> the object ID of a tracking reference.
>
> Pass the repository to unique_tracking_name() and through
> tracking_name_data. Callers pass the_repository for now.

You could be more descriptive more about the patches, someone should be able to go through the commit and sort get the whole idea of the patch, what was present, What changes and why ?

Otherwise, the changes look good to me.
>
> This removes the need for USE_THE_REPOSITORY_VARIABLE in checkout.c.
>
Thanks.
Previous: Okhuomon AjayiNext: Okhuomon Ajayi
Message 2 of 14 in “checkout: use repository parameter in unique_tracking_name”
  1. checkout: use repository parameter in unique_tracking_nameOkhuomon Ajayi, Oct 17, 2026
  2. Usman AkinyemiOct 22, 2026
  3. Okhuomon AjayiOct 22, 2026
  4. checkout: pass the repository to unique_tracking_name()Okhuomon Ajayi, Oct 22, 2026
  5. Junio C HamanoOct 22, 2026
  6. Junio C HamanoOct 22, 2026
  7. Okhuomon AjayiOct 22, 2026
  8. 0/2 checkout: make unique_tracking_name() use the given repositoryOkhuomon Ajayi, Oct 23, 2026
  9. 1/2 remote: add repo_for_each_remote()Okhuomon Ajayi, Oct 23, 2026
  10. Christian CouderNov 3, 2026
  11. 2/2 checkout: pass the repository to unique_tracking_name()Okhuomon Ajayi, Oct 23, 2026
  12. 0/2 checkout: make unique_tracking_name() use the given repositoryOkhuomon Ajayi, Nov 4, 2026
  13. 1/2 remote: add repo_for_each_remote()Okhuomon Ajayi, Nov 4, 2026
  14. 2/2 checkout: pass the repository to unique_tracking_name()Okhuomon Ajayi, Nov 4, 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.