Re: Unable to clone empty repositories remotely

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Hannu Koivisto
Date: Wednesday, November 26, 2008 - 6:13 am

"Christian MICHON" <christian.michon@gmail.com> writes:


No, it wouldn't.  I don't doubt that there are workarounds - I
mentioned one possibility myself.  Admittedly your workaround may
be more convenient than mine, but it's still a workaround.

Now that I think of it, I wonder if one could go one step further
in shared repository creation usability and make it possible to do
that git init step remotely as well (I mean, directly with a
one-step git command instead of ssh host "cd /repos ; mkdir foo ;
cd foo; git init ...").  Since git init doesn't take non-option
arguments, I suppose it could be extended to accept ssh (and file)
urls for this purpose?  And maybe an option to create a
corresponding local clone at the same time.

-- 
Hannu
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Unable to clone empty repositories remotely, Hannu Koivisto, (Tue Nov 25, 2:05 pm)
Re: Unable to clone empty repositories remotely, Christian MICHON, (Tue Nov 25, 2:33 pm)
Re: Unable to clone empty repositories remotely, Hannu Koivisto, (Wed Nov 26, 6:13 am)