Re: git?

That *is* the syntax I suggested. :-) Your example just doesn’t
include a user name, which of course is fine if ssh DTRT in that
regard.

> > Next, git-pull is actually git-fetch (which downloads commits
> > you are missing) *plus* git-merge. Because of the latter, you
> > have to say which branch you want to merge. And since
> > git-pull is used to merge changes from a remote branch, and
> > you can have several remotes configured (it's a DVCS!), you
> > also have to specify which remote, to make it unambiguous. So
> > based on the above you'd say
>
> Only if the current workin branch doesnt have a remote defined
> for it. In which case 'git pull' will work fine.

Ah. I guess in the few cases where I’ve used it, I set up my
branch in a way that doesn’t do that automatically, so I didn’t
know that it would.

> > If you have push access to all of your remotes, and you want
> > to push to all, you can also pass `--all` instead of a
> > particular remote.
>
> Huh? --all is documented as pushing all refs to the remote
> specified. Not pushing to all remotes. Have i missed a trick
> here?

Woops, you are right.

> Hrm, I didnt know that you could define multiple urls for a
> single remote. That seems a bit strange to me.

Strange maybe, but extremely useful! Makes it very easy to deal
with multiple repos that you _publish_ to (vs the ones you
actually muck around in), or even multiple sets of them (if your
workflow is so defined).

Regards,