From: Robert Coup <robert@coup.net.nz>
To: Tao Klerks <tao@klerks.biz>
Cc: git <git@vger.kernel.org>
Subject: Re: "git fetch --refetch" and multiple (separate/orphan) branches
Date: Sat, 3 Jun 2023 09:18:43 +0100 [thread overview]
Message-ID: <CACf-nVfUotaTYeCC9XMvnYYNhjX+EW89z7fhUX0Ok9TpsVTRTw@mail.gmail.com> (raw)
In-Reply-To: <CAPMMpoiJ4cNcAR9gO5d-749N3YW-88p1gMnX8ySGgz84Mr9coA@mail.gmail.com>
Hi Tao
On Fri, 2 Jun 2023 at 22:23, Tao Klerks <tao@klerks.biz> wrote:
> What I believe is happening is that *if* there are refs to be updated
> (or new refs, presumably), *then* the objects returned to the client
> are only those required for those refs. If, on the other hand, there
> are no updated refs, then you get what is advertised in the doc: "all
> objects as a fresh clone would [...]".
>
> I've tested a couple of different scenarios and the behavior seems
> consistent with this explanation.
Do you have a repo & steps that could reproduce this easily? Otherwise
I can try and work up something.
> Is this a bug, or expected behavior that should be noted in the doc,
> or do we consider the multiple-independent-branches usecase to be
> edge-casey enough to be an easter egg for people like me?
At first glance it appears to be a bug.
Thanks,
Rob :)
next prev parent reply other threads:[~2023-06-03 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 21:22 "git fetch --refetch" and multiple (separate/orphan) branches Tao Klerks
2023-06-03 8:18 ` Robert Coup [this message]
2023-08-10 7:14 ` Tao Klerks
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=CACf-nVfUotaTYeCC9XMvnYYNhjX+EW89z7fhUX0Ok9TpsVTRTw@mail.gmail.com \
--to=robert@coup.net.nz \
--cc=git@vger.kernel.org \
--cc=tao@klerks.biz \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).