From: Paolo Bonzini <pbonzini@redhat.com>
To: "Junio C Hamano" <gitster@pobox.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Linux List Kernel Mailing" <linux-kernel@vger.kernel.org>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"KVM list" <kvm@vger.kernel.org>,
"Michael Haggerty" <mhagger@alum.mit.edu>
Subject: Re: [RFC/PATCH] refs: tone down the dwimmery in refname_match() for {heads,tags,remotes}/*
Date: Mon, 27 May 2019 17:44:07 +0200 [thread overview]
Message-ID: <a40c5388-4274-6bfa-4213-6013601c8fae@redhat.com> (raw)
In-Reply-To: <xmqqef4jewj6.fsf@gitster-ct.c.googlers.com>
On 27/05/19 17:39, Junio C Hamano wrote:
> I do not think lightweight vs annotated should be the issue. The
> tag that the requestor asks to be pulled (from repository ../b)
> should be what the requestor has locally when writing the request
> (in repository .). Even if both tags at remote and local are
> annotated, we should still warn if they are different objects, no?
Right, lightweight vs annotated then is the obvious special case where
one of the two is a commit and the other is a tag, hence they ought not
to have the same SHA1. I'll take a look.
Paolo
next prev parent reply other threads:[~2019-05-27 15:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-26 9:55 [GIT PULL] KVM changes for Linux 5.2-rc2 Paolo Bonzini
2019-05-26 15:51 ` Linus Torvalds
2019-05-26 17:53 ` Paolo Bonzini
2019-05-26 20:49 ` Linus Torvalds
2019-05-26 22:54 ` [RFC/PATCH] refs: tone down the dwimmery in refname_match() for {heads,tags,remotes}/* Ævar Arnfjörð Bjarmason
2019-05-27 12:33 ` Paolo Bonzini
2019-05-27 14:29 ` Ævar Arnfjörð Bjarmason
2019-05-27 15:39 ` Junio C Hamano
2019-05-27 15:44 ` Paolo Bonzini [this message]
2019-06-21 14:44 ` [PATCH] push: make "HEAD:tags/my-tag" consistently push to a branch Ævar Arnfjörð Bjarmason
2019-06-21 16:05 ` Junio C Hamano
2019-05-26 20:55 ` [GIT PULL] KVM changes for Linux 5.2-rc2 pr-tracker-bot
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=a40c5388-4274-6bfa-4213-6013601c8fae@redhat.com \
--to=pbonzini@redhat.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
--cc=rkrcmar@redhat.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®