Josef Weidendorfer [off-list ref] writes:
quoted
$ 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
I am not convinced myself that default/persistent mapping makes
much sense, and updating the stored mappings dynamically when
the user uses non-default mappings in push/pull as a one-shot
operation does not make any sense at all at least to me. You
should rather consider that the current specification does not
deal with (1) at all. The set of default pull/push refs does
not make much sense without mappings for them, so that is what
the file records.
On Saturday 20 August 2005 20:54, Junio C Hamano wrote:
Josef Weidendorfer [off-list ref] writes:
quoted
quoted
$ 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
I am not convinced myself that default/persistent mapping makes
much sense,
I think that both, default and non-default persistant mappings, are only a
handy convenience issue for less typing. If GIT core is not doing this, some
(most?) porcelains will invent their own way for storing these mappings (like
Cogito is doing with branches/). I think it is better if this is
"standardized".
Currently missing here is automatic detection of the remote repository for a
given head to be pulled/pushed. But this is no format issue.
and updating the stored mappings dynamically when
the user uses non-default mappings in push/pull as a one-shot
operation does not make any sense at all at least to me.
Yes, you are right.
Josef
Josef Weidendorfer [off-list ref] writes:
I think that both, default and non-default persistant
mappings, are only a handy convenience issue for less
typing. If GIT core is not doing this, some (most?) porcelains
will invent their own way for storing these mappings (like
Cogito is doing with branches/). I think it is better if this
is "standardized".
I agree in principle, and it should not be hard to add support
for optional "Default-pull" and "Default-push" keywords to
remotes/ files (lack of which means to use LHS of refspecs on
"Pull" or "Push" lines) to git-parse-remote-script. Patches
welcome.
Currently missing here is automatic detection of the remote
repository for a given head to be pulled/pushed. But this is
no format issue.
"git ls-remote <repo>" perhaps?