From: Stefan Sperling <stsp@stsp.name>
Subject: Re: introducing gotadmin dump
To: Omar Polo <op@omarpolo.com>
Cc: gameoftrees@openbsd.org
Date: Thu, 6 Jul 2023 22:19:23 +0200

On Thu, Jul 06, 2023 at 05:51:10PM +0200, Omar Polo wrote:
>  add an initial implementation of gotadmin dump

ok stsp@

I am pondering some questions about object selection for future work:

- Should gotadmin dump -x accept commit IDs in addition to reference names?
  Users might want to generate incremental dumps relative to some commit(s)
  without having to create a reference first.

- Should we dump refs in the refs/got/ namespace if they are mentioned on the
  command line? In other words, should we only ever filter such refs out when
  they were picked implicitly via a listing of all refs?
  Such that refs/got/backup could be saved in a bundle, for example?

- In addition to refs/got/ should gotadmin dump ignore the refs/remotes/
  namespace, at least by default? Currently refs/remotes/ appears in the bundle.
  I am unsure whether dumping remote refs is very useful in general, but maybe
  some people do find it useful, e.g. when keeping a copy of some remote branch
  to merge commits from.

- Maybe some people would really like to dump everything?
  Should we have a flag (-a?) to force dumping of everything referenced,
  including refs/remotes and refs/got?