From: Junio C Hamano <gitster@pobox.com>
To: Philip Oakley <philipoakley@iee.email>
Cc: Git List <git@vger.kernel.org>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
Andreas Krey <a.krey@gmx.de>
Subject: Re: Idea: Git Bundle V3 capability @HEAD=ref/heads/<name>
Date: Thu, 06 Oct 2022 11:45:38 -0700 [thread overview]
Message-ID: <xmqq7d1clrjh.fsf@gitster.g> (raw)
In-Reply-To: <037901f1-1649-1485-a853-9783b9d43b31@iee.email> (Philip Oakley's message of "Thu, 6 Oct 2022 16:55:49 +0100")
Philip Oakley <philipoakley@iee.email> writes:
> In brian's recent work on V3 bundles [1, et al] I spotted a potential
> idea for resolving the long standing problem that the bundle code may
> need to guess at which ref HEAD was pointed [2, et al] at when there
> were two branches that pointed at the same HEAD oid.
>
> The basic idea is to utilise the new 'capabilities' field to pass the
> particular ref that is HEAD using a 'HEAD' capability
> i.e. sending the capability @HEAD=ref/heads/<name>
Whatever you do, I think it should model what the protocol between
"git fetch" and "git upload-pack" use to convey where the symbolic
refs point at.
next prev parent reply other threads:[~2022-10-06 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8d88ba68-4585-634b-1fe0-61c3465fa682@iee.email>
2022-10-06 15:55 ` Idea: Git Bundle V3 capability @HEAD=ref/heads/<name> Philip Oakley
2022-10-06 18:45 ` Junio C Hamano [this message]
2022-10-07 9:02 ` brian m. carlson
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=xmqq7d1clrjh.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=a.krey@gmx.de \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.email \
--cc=sandals@crustytoothpaste.net \
/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.