From: Johannes Sixt <j6t@kdbg.org>
To: Han Jiang <jhcarl0814@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: `git fetch --refmap=<refspec>… <repository> <refspec>… ` providing NON-empty <refspec> to the --refmap ALSO causes Git to ignore the configured refspecs
Date: Wed, 4 Sep 2024 08:15:44 +0200 [thread overview]
Message-ID: <a33a73f7-e6dd-4f97-a635-c6c5dfcadeb1@kdbg.org> (raw)
In-Reply-To: <CANrWfmSe0ekbRR9VsX8jALWQQVdhDv-2WTSm47jHTiV9-Z7-pg@mail.gmail.com>
Am 04.09.24 um 06:09 schrieb Han Jiang:
> What did you expect to happen? (Expected behavior)
>
> In `git fetch --refmap='+refs/heads/branch1:refs/remotes/server/branch1'
> server branch1 branch2`,
> `remote.server.fetch=+refs/heads/*:refs/remotes/server/*` merges with
> `--refmap='+refs/heads/branch1:refs/remotes/server/branch1'`,
The way I read the documentation of --refmap, I cannot infer any sort of
merging of refspec, only that a replacement occurs.
> so these should be what would be done:
> branch1 -> server/branch1
> branch2 -> server/branch2
>
> What happened instead? (Actual behavior)
>
> In `git fetch --refmap='+refs/heads/branch1:refs/remotes/server/branch1'
> server branch1 branch2`,
> `remote.server.fetch=+refs/heads/*:refs/remotes/server/*` is replaced
> by `--refmap='+refs/heads/branch1:refs/remotes/server/branch1'`,
> so these are what would be done:
> branch1 -> server/branch1
So, this seems the correct output, because it is no longer specified how
branch2 should be stored locally.
-- Hannes
next prev parent reply other threads:[~2024-09-04 6:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 4:09 `git fetch --refmap=<refspec>… <repository> <refspec>…` providing NON-empty <refspec> to the --refmap ALSO causes Git to ignore the configured refspecs Han Jiang
2024-09-04 6:15 ` Johannes Sixt [this message]
2024-09-04 11:12 ` `git fetch --refmap=<refspec>… <repository> <refspec>… ` " Han Jiang
2024-09-04 16:38 ` Johannes Sixt
2024-09-04 16:47 ` Junio C Hamano
2024-09-04 23:52 ` Han Jiang
2024-09-04 14:34 ` `git fetch --refmap=<refspec>… <repository> <refspec>…` " Junio C Hamano
2024-09-04 23:41 ` Han Jiang
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=a33a73f7-e6dd-4f97-a635-c6c5dfcadeb1@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.org \
--cc=jhcarl0814@gmail.com \
/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).