Karthik Nayak <karthik.188@xxxxxxxxx> writes: > Thanks all for the discussion, I'll try to summarize the path forward > as per my understanding. It has already been clear for the past 5 years or so since 3a3b9d8c (refs: new ref types to make per-worktree refs visible to all worktrees, 2018-10-21) that we need to treat "worktrees/foo/HEAD", "worktrees/bar/refs/bisect/bad", etc. as something end-users can access via the normal ref mechansim (by a resolve_ref() call that is eventually made from get_sha1() when these are passed to say "git log"); I just did not remember that one but that does not mean we can suddenly change the rules. So you'd probably need to tweak the end of your bullet point #3, but other than that it is a great summary. Thanks. > 1. We want to introduce a way to output all refs. This includes refs > under "refs/", pseudo refs, HEAD, and any other ref like objects under > $GIT_DIR. The reasoning being that users are allowed currently to create > refs without any directory restrictions. So with the upcoming reftable > backend, it becomes important to provide a utility to print all the refs > held in the reftable. Ideally we want to restrict such ref's from being > created but for the time being, since thats allowed, we should also > provide the utility to print such refs. > > 2. In the files backend, this would involve iterating through the > $GIT_DIR and finding all ref-like objects and printing them. > > 3. To expose this to the user, we could do something like > > $ git for-each-ref "" > > Which is a natural extension of the current syntax, where the empty > string would imply that we do not filter to the "refs/" directory. > It is still not clear whether we should support "worktrees". > > Any corrections here?
