On Tue, Jun 23, 2020 at 12:03 AM Han-Wen Nienhuys <hanwen@xxxxxxxxxx> wrote:
> The bottom 2 commits should be OK to merge as is into next.
> ("checkout: add '\n' to reflog message", "lib-t6000.sh: write tag
> using git-update-ref")
The patch t3432: use git-reflog to inspect the reflog for HEAD can
also be merged as is.
> The major open question is how to handle per-worktree refs. My idea
> is that, on creation, the reftable backend can figure out if it is
> running in a worktree or in the main repository. If it is running in
> worktree X, we could read/write pseudorefs as ~X/PSEUDO_REF.
I figured out a better way to do this. See the series that I am posting today.
Test failures are down to 556.
> Could we discuss next steps for merging at least the library? I think
> that would solve one of the major complaints, which is that history is
> kept in a separate repository.
anyone? Junio, Jonathan?
--
Han-Wen Nienhuys - Google Munich
I work 80%. Don't expect answers from me on Fridays.
--
Google Germany GmbH, Erika-Mann-Strasse 33, 80636 Munich
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
