From: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>
To: git@vger.kernel.org
Subject: Re: Multi-head pulling series
Date: Thu, 18 Aug 2005 12:45:58 +0200 [thread overview]
Message-ID: <200508181245.58250.Josef.Weidendorfer@gmx.de> (raw)
In-Reply-To: <7vek8rlnbn.fsf@assigned-by-dhcp.cox.net>
On Thursday 18 August 2005 09:24, Junio C Hamano wrote:
> $ cat $GIT_DIR/remotes/www
> URL: http://www.kernel.org/pub/scm/git/git.git/
> Pull: master:ko-master pu:ko-pu
> Push: master:master pu:pu foo:bar
Isn't this mixing two kinds of information:
1) Some default/persistent mapping of local to remote heads
2) The default heads which are pulled/pushed when only giving the remote, like
in:
> $ git push mko ;# push our master and pu to the same
> # name, foo to .git/refs/heads/bar.
I think it makes sense to be able to store mappings without adding the head to
the default group of heads pulled.
Can we put the default pull/push actions in separate lines, like
$ cat $GIT_DIR/remotes/mko
URL: master.kernel.org:/pub/scm/git/git.git/
Pull: master:ko-master pu:ko-pu mylocal:myremote
Push: master:master pu:pu foo:bar
Default-Pull: master pu
Default-Push: master pu foo
> $ git push mko pu:refs/heads/testing
> # instead of pushing to the usual ref,
> # push our pu to refs/heads/testing,
> # this time only.
With a command (push/fetch/pull) giving an explicit local/remote mapping, it
would be cool to automatically add the given mapping to the remotes/ file if
there is no push-mapping for pu yet, so that you can have the same later with
only
git push mko pu
And finally, it would be nice to specify a default mapping for arbitrary heads
$ cat $GIT_DIR/remotes/www
URL: http://www.kernel.org/pub/scm/git/git.git/
Pull: www#*:*
Such that
git fetch www#pu
will fetch head pu into local head .refs/heads/www#pu
Josef
PS: I know I should provide patches for my proposals. But let discuss them
first.
next prev parent reply other threads:[~2005-08-18 10:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 7:24 Multi-head pulling series Junio C Hamano
2005-08-18 7:39 ` [PATCH 1/3] Start adding the $GIT_DIR/remotes/ support Junio C Hamano
2005-08-18 7:39 ` [PATCH 2/3] Multi-head fetch Junio C Hamano
2005-08-18 7:39 ` [PATCH 3/3] Update git-pull to match updated git-fetch Junio C Hamano
2005-08-18 10:45 ` Josef Weidendorfer [this message]
2005-08-20 18:54 ` Multi-head pulling series Junio C Hamano
2005-08-22 16:35 ` Josef Weidendorfer
2005-08-23 1:07 ` Junio C Hamano
2005-08-23 5:37 ` Junio C Hamano
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=200508181245.58250.Josef.Weidendorfer@gmx.de \
--to=josef.weidendorfer@gmx.de \
--cc=git@vger.kernel.org \
/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).