All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Han-Wen Nienhuys via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Han-Wen Nienhuys <hanwenn@gmail.com>
Subject: [PATCH 0/6] Refs cleanup
Date: Wed, 20 May 2020 17:36:06 +0000	[thread overview]
Message-ID: <pull.638.git.1589996173.gitgitgadget@gmail.com> (raw)

This patch series contains preliminary cleanups for adding reftable support
to git-core

Han-Wen Nienhuys (5):
  refs.h: clarify reflog iteration order
  t: use update-ref and show-ref to reading/writing refs
  refs: improve documentation for ref iterator
  reftable: clarify how empty tables should be written
  reftable: define version 2 of the spec to accomodate SHA256

Jonathan Nieder (1):
  reftable: file format documentation

 Documentation/Makefile               |    1 +
 Documentation/technical/reftable.txt | 1083 ++++++++++++++++++++++++++
 refs.h                               |   18 +-
 refs/refs-internal.h                 |   18 +-
 t/t0002-gitfile.sh                   |    2 +-
 t/t1400-update-ref.sh                |   32 +-
 t/t1506-rev-parse-diagnosis.sh       |    2 +-
 t/t6050-replace.sh                   |    2 +-
 t/t9020-remote-svn.sh                |    4 +-
 9 files changed, 1137 insertions(+), 25 deletions(-)
 create mode 100644 Documentation/technical/reftable.txt


base-commit: b34789c0b0d3b137f0bb516b417bd8d75e0cb306
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-638%2Fhanwen%2Frefs-cleanup-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-638/hanwen/refs-cleanup-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/638
-- 
gitgitgadget

             reply	other threads:[~2020-05-20 17:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 17:36 Han-Wen Nienhuys via GitGitGadget [this message]
2020-05-20 17:36 ` [PATCH 1/6] refs.h: clarify reflog iteration order Han-Wen Nienhuys via GitGitGadget
2020-05-20 17:36 ` [PATCH 2/6] t: use update-ref and show-ref to reading/writing refs Han-Wen Nienhuys via GitGitGadget
2020-05-20 17:36 ` [PATCH 3/6] refs: improve documentation for ref iterator Han-Wen Nienhuys via GitGitGadget
2020-05-20 17:36 ` [PATCH 4/6] reftable: file format documentation Jonathan Nieder via GitGitGadget
2020-05-20 17:36 ` [PATCH 5/6] reftable: clarify how empty tables should be written Han-Wen Nienhuys via GitGitGadget
2020-05-20 17:36 ` [PATCH 6/6] reftable: define version 2 of the spec to accomodate SHA256 Han-Wen Nienhuys via GitGitGadget
2020-05-20 17:46 ` [PATCH 0/6] Refs cleanup Junio C Hamano

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=pull.638.git.1589996173.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=hanwenn@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.