From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Daniel Martí" <mvdan@mvdan.cc>, git@vger.kernel.org
Subject: Re: mirror clone does not keep HEAD updated
Date: Tue, 4 Apr 2023 20:56:18 -0500 [thread overview]
Message-ID: <CAMP44s1DrFY7ZxfdFwVDd=uJpdxkEDf8irAzEKmcih2MEuv0Aw@mail.gmail.com> (raw)
In-Reply-To: <xmqqileb1u34.fsf@gitster.g>
On Tue, Apr 4, 2023 at 12:07 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> Daniel Martí <mvdan@mvdan.cc> writes:
>
> > I'm testing `git clone --mirror` to properly mirror a repository on
> > github.com. It appears to be working well, except for keeping HEAD
> > correctly in place.
>
> There is no such feature in "git clone" or "git fetch" to check what
> branch the remote HEAD is pointing at and move the local copy around.
Only because you didn't merge the patches I sent a while ago [1].
> Modern versions of Git these days have a protocol level support to
> convey that information, and I think it is feasible to invent such a
> feature to automatically repoint refs/remotes/$remote/HEAD to
> whatever remote-tracking branch found in the refs/remotes/$remote/
> hierarchy.
Or just repoint it to the remote's HEAD, which is what everyone expects.
> We are pretty much "somebody should initiate the process to scratch
> their own itch, and we will help them in doing so" community, so you
> or somebody who reads this thread interesting will hopefully start
> such an effort ;-)
That has not been my experience. Even when I scratch somebody else's
itch, there is not much help, and the patches don't end up being
merged.
Cheers.
[1] https://lore.kernel.org/git/20201118091219.3341585-1-felipe.contreras@gmail.com/
--
Felipe Contreras
next prev parent reply other threads:[~2023-04-05 1:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 16:16 mirror clone does not keep HEAD updated Daniel Martí
2023-04-04 16:38 ` Junio C Hamano
2023-04-05 1:56 ` Felipe Contreras [this message]
2023-04-05 1:38 ` Felipe Contreras
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='CAMP44s1DrFY7ZxfdFwVDd=uJpdxkEDf8irAzEKmcih2MEuv0Aw@mail.gmail.com' \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mvdan@mvdan.cc \
/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 NNTP newsgroup(s).