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

The most efficient way to test if repositories share the same objects

From
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Date
Mar 22, 2018, 16:48 UTC
Message-ID
<14d0937f-0e39-7af7-a395-3046ec5d5c16@linuxfoundation.org>
Hi, all:

What is the most efficient way to test if repoA and repoB share common commits? My goal is to automatically figure out if repoB can benefit from setting alternates to repoA and repacking. I currently do it by comparing the output of "show-ref --tags -s", but that does not work for repos without tags.

Best,
-- 
Konstantin Ryabitsev
Next: Ævar Arnfjörð Bjarmason
Message 1 of 8 in “The most efficient way to test if repositories share the same objects”
  1. Konstantin RyabitsevMar 22, 2018
  2. Ævar Arnfjörð BjarmasonMar 22, 2018
  3. Junio C HamanoMar 22, 2018
  4. Ævar Arnfjörð BjarmasonMar 22, 2018
  5. Konstantin RyabitsevMar 22, 2018
  6. Junio C HamanoMar 22, 2018
  7. Konstantin RyabitsevMar 23, 2018
  8. Ævar Arnfjörð BjarmasonMar 23, 2018

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.