Il 26/05/2013 20:14, John Keeping ha scritto:
On Sun, May 26, 2013 at 08:09:56PM +0200, Gioele Barabucci wrote:
Il 26/05/2013 20:00, Andreas Schwab ha scritto:
Simple, I keep all my projects on the same server, so I would like to
refer to that server + path using 'remote-repo'.
"git+ssh://git.example.org//users/gioele/projects" insteadOf "remote-repo"
In what way do you think that `git remote add` handles the path?
All `git remote add` does is add a new "remote.<name>.url" entry to the
configuration file with the value as given on the command line. The
insteadOf mapping will only be applied when you try to fetch from/push
to the remote.
Regardless of the implementation of the commands, if I do
mkdir projectA
cd projectA
git init .
git remote add origin remote-repo/projectA.git
git pull origin master
I get a working repository. If I do
git clone remote-repo/projectA.git
all I will get is an error.
I do not see any reason (UX-wise) why the two sequences of commands
shouldn't work the same when used on the same URL.
Regards,
--
Gioele Barabucci <gioele@xxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html