From: Junio C Hamano <gitster@pobox•com>
To: Marc Branchaud <marcnarc@xiplink•com>
Cc: git@vger•kernel.org
Subject: Re: [PATCH v2 9/9] fetch: allow explicit --refmap to override configuration
Date: Thu, 05 Jun 2014 11:36:56 -0700 [thread overview]
Message-ID: <xmqqy4xbrynr.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <539090AD.9040100@xiplink.com> (Marc Branchaud's message of "Thu, 05 Jun 2014 11:45:49 -0400")
Marc Branchaud <marcnarc@xiplink•com> writes:
> I don't have any objection to the option per se. But I do wonder if there's
> a need to add yet another knob to git just for completeness. Has anyone ever
> needed this?
It is not a good yardstick, as everybody has survived without it
since Git's inception. The right question to ask is: would it help
new use patterns, or improve existing use patterns?
Two possible scenarios I can think of offhand are
* using an empty refmap to ensure that your "fetch" this time is
really ephemeral without affecting the longer-term configured
remote-tracking branches
* grabbing only a few selected branches out of hundreds, e.g.
$ git fetch https://github.com/gitster/git \
--refmap=refs/heads/*:refs/remotes/jch/* maint master next +pu
instead of having to spell its long-hand
$ git fetch https://github.com/gitster/git \
refs/heads/maint:refs/remotes/jch/maint \
refs/heads/master:refs/remotes/jch/master \
refs/heads/next:refs/remotes/jch/next \
+refs/heads/pu:refs/remotes/jch/pu
but there may be more useful scenarios other people can come up
with ;-).
next prev parent reply other threads:[~2014-06-05 18:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 22:16 [PATCH v2 0/9] Clarify two uses of remote.*.fetch Junio C Hamano
2014-06-03 22:16 ` [PATCH v2 1/9] fetch doc: update introductory part for clarity Junio C Hamano
2014-06-03 22:16 ` [PATCH v2 2/9] fetch doc: move FETCH_HEAD material lower and add an example Junio C Hamano
2014-06-03 22:16 ` [PATCH v2 3/9] fetch doc: update note on '+' in front of the refspec Junio C Hamano
2014-06-18 7:56 ` Michael Haggerty
2014-06-03 22:16 ` [PATCH v2 4/9] fetch doc: remove notes on outdated "mixed layout" Junio C Hamano
2014-06-03 22:16 ` [PATCH v2 5/9] fetch doc: on pulling multiple refspecs Junio C Hamano
2014-06-04 14:44 ` Marc Branchaud
2014-06-03 22:16 ` [PATCH v2 6/9] fetch doc: update refspec format description Junio C Hamano
2014-06-03 22:16 ` [PATCH v2 7/9] fetch doc: remove "short-cut" section Junio C Hamano
2014-06-04 14:46 ` Marc Branchaud
2014-06-03 22:16 ` [PATCH v2 8/9] fetch doc: add a section on configured remote-tracking branches Junio C Hamano
2014-06-04 14:55 ` Marc Branchaud
2014-06-04 22:17 ` Junio C Hamano
2014-06-05 15:29 ` Marc Branchaud
2014-06-05 15:40 ` [PATCH] docs: Explain the purpose of fetch's and pull's <refspec> parameter Marc Branchaud
2014-06-05 22:12 ` Junio C Hamano
2014-06-11 14:24 ` Marc Branchaud
2014-06-03 22:16 ` [PATCH v2 9/9] fetch: allow explicit --refmap to override configuration Junio C Hamano
2014-06-04 15:01 ` Marc Branchaud
2014-06-04 22:28 ` Junio C Hamano
2014-06-05 15:45 ` Marc Branchaud
2014-06-05 18:36 ` Junio C Hamano [this message]
2014-06-18 12:21 ` Michael Haggerty
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=xmqqy4xbrynr.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=marcnarc@xiplink$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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