mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <>
To: Konstantin Ryabitsev <>
Subject: Re: The most efficient way to test if repositories share the same objects
Date: Thu, 22 Mar 2018 20:20:45 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, Mar 22 2018, Konstantin Ryabitsev wrote:

> 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.

If you're using show-ref already to get the tag tips, you can use
for-each-ref to get all tips.

But of course that'll just give you the tips. You could then use `git
cat-file --batch-check` on both ends to see what commits from the other
they report knowing about, in case they have branches that are
ahead/behind the other.

  reply	other threads:[~2018-03-22 19:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-22 16:48 The most efficient way to test if repositories share the same objects Konstantin Ryabitsev
2018-03-22 19:20 ` Ævar Arnfjörð Bjarmason [this message]
2018-03-22 19:35   ` Junio C Hamano
2018-03-22 19:53     ` Ævar Arnfjörð Bjarmason
2018-03-22 21:32     ` Konstantin Ryabitsev
2018-03-22 21:44       ` Junio C Hamano
2018-03-23 13:57         ` Konstantin Ryabitsev
2018-03-23 14:36           ` Ævar Arnfjörð Bjarmason

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).