On Sun, Jan 11, 2009 at 12:24 PM, Chris Wanstrath <[email protected]> wrote:

>
> On Fri, Jan 9, 2009 at 5:27 PM, Sitaram Chamarty <[email protected]>
> wrote:
>
> > I just found that the following commands do not work:
> > (1) git clone 
> > ssh://[email protected]/~git/sitaramc/git-notes.git<http://[email protected]/%7Egit/sitaramc/git-notes.git>
> > (2) git clone 
> > ssh://[email protected]/~/sitaramc/git-notes.git<http://[email protected]/%7E/sitaramc/git-notes.git>
> > (3) git clone ssh://[email protected]/sitaramc/git-notes.git
> >
> > However, this one works:
> >
> > (4) git clone [email protected]:sitaramc/git-notes.git
> >
> > As far as I know, this is the same as #1 and #2 (tested with my own repos
> > via ssh).
>
> #4 is not the same as #1 and #2. #1 and #2 both provide an absolute
> path to a location on disk, #4 provides an argument
> ("sitarmc/git-notes.git").
>
> We will never support any format but #4.
>

Oh that's ok -- I did mention very specifically in my original email that
I'm only trying to reconcile my understanding of how these URLs work, and
*not* asking for any changes :-)

Indeed I'd like to know how you can make #4 be merely an argument.
Everything I try on my internal servers just makes it behave like a relative
path (relative to the user's home that is, so you could also say it's
absolute, if you wished to describe #1 and #2 as absolute).

Is there some option I'm missing which would let me do that?

In other words, how can I have a repo located at some location of my
choosing, but the user accesses it by some standard/canonical argument.

Any pointers to how to do this would be greatly appreciated.

Thanks,

Sitaram

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"GitHub" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/github?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to