All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Nielsen <adam.nielsen@uq.edu.au>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Unable to get "pretty" URL aliases working
Date: Thu, 14 Jan 2010 10:45:59 +1000	[thread overview]
Message-ID: <4B4E6947.2020009@uq.edu.au> (raw)
In-Reply-To: <7vockytrwy.fsf@alter.siamese.dyndns.org>

>> What actually happens when you use the ssh:// style connection?
> 
> Be it ssh://host/full/path or host:/full/path or host:path/in/home, you
> log in as whatver ssh identifies you as to the server, and start a
> server-side git process over there.

Ah ok, that makes more sense.  Strange then if it's a server-side git 
process that it ignores the server's /etc/gitconfig where aliases can be 
set up.

> With ssh://host/path notation, there is no way to specify any relative
> path (i.e. "/path" part begins at root) so it will mean the same thing for
> everybody (unless you are getting chrooted or something), while host:path
> notation allows relative path which will be taken relative as where you
> are, i.e. home directory of the user on the server.

In that case I symlinked my repository folder to /git so that SSH users 
can "cd /git/project.git" and this seems to work well.  I can now use 
git URLs like ssh://server/git/project.git even though the repos are 
buried much deeper down in the tree.

Thanks for the explanations!

Cheers,
Adam.

      reply	other threads:[~2010-01-14  0:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11  5:57 Unable to get "pretty" URL aliases working Adam Nielsen
2010-01-11  7:46 ` Johannes Sixt
2010-01-11  7:59 ` Junio C Hamano
2010-01-11 23:23   ` Adam Nielsen
2010-01-13  6:55     ` Junio C Hamano
2010-01-14  0:45       ` Adam Nielsen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B4E6947.2020009@uq.edu.au \
    --to=adam.nielsen@uq.edu.au \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.