From: Jonathan Tan <jonathantanmy@google.com>
To: git@vger.kernel.org
Cc: Jonathan Tan <jonathantanmy@google.com>
Subject: [PATCH 0/2] Annotated tags pointing to missing but promised blobs
Date: Thu, 12 Jul 2018 17:03:05 -0700 [thread overview]
Message-ID: <cover.1531438861.git.jonathantanmy@google.com> (raw)
These are based on jt/partial-clone-fsck-connectivity.
The patches in jt/partial-clone-fsck-connectivity were motivated by bugs
I discovered in partial clones when refs pointed to blobs directly.
While continuing to work on this, I noticed issues with annotated tags -
that is, refs pointing to tags pointing to blobs. Here are some fixes.
Jonathan Tan (2):
revision: tolerate promised targets of tags
tag: don't warn if target is missing but promised
revision.c | 3 +++
t/t5616-partial-clone.sh | 44 ++++++++++++++++++++++++++++++++++++++++
tag.c | 13 +++++++++---
3 files changed, 57 insertions(+), 3 deletions(-)
--
2.18.0.203.gfac676dfb9-goog
next reply other threads:[~2018-07-13 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 0:03 Jonathan Tan [this message]
2018-07-13 0:03 ` [PATCH 1/2] revision: tolerate promised targets of tags Jonathan Tan
2018-07-13 0:03 ` [PATCH 2/2] tag: don't warn if target is missing but promised Jonathan Tan
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=cover.1531438861.git.jonathantanmy@google.com \
--to=jonathantanmy@google.com \
--cc=git@vger.kernel.org \
/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.