From: Jakub Narebski <jnareb@gmail.com>
To: Petr Baudis <pasky@suse.cz>
Cc: Sven Verdoolaege <skimo@liacs.nl>, git@vger.kernel.org
Subject: Re: repo.or.cz wishes?
Date: Mon, 27 Aug 2007 23:58:42 +0200 [thread overview]
Message-ID: <200708272358.43021.jnareb@gmail.com> (raw)
In-Reply-To: <20070827004153.GN1219@pasky.or.cz>
On Monday, 27 August 2007, Petr "Pasky" Baudis wrote:
> On Mon, Aug 27, 2007 at 02:16:34AM CEST, Sven Verdoolaege wrote:
>> On Mon, Aug 27, 2007 at 01:59:44AM +0200, Petr Baudis wrote:
>>>
>>> So now I wonder, what is the thing you miss most there? Any cool stuff
>>> repo.or.cz could (preferrably easily) do and doesn't?
Is it now possible to _upload_ SSH key, instad of copy'n'paste it
when creating repository/account?
Would it be reasonable to limit repository name length, or at least
modify gitweb to truncate (cut) it if it is too long?
>> Just a minor nit, but how about dropping the "git+" from the
>> Push URL?
>
> I'm a major proponent of the "git+" - it's just the correct thing to
> specify. ssh:// by itself means secure _shell_, and that's not what the
> URL means - ssh is literaily just a transport layer for the git
> protocol. This is not my invention but fairly standard thing which
> plenty of people use, and it makes it possible to select proper protocol
> handlers and so on, shall something generic crunch on the URL. I've
> never actually understood why do some people dislike it.
First, it is in the context of git, so one can say that "git+" is
implied. Documentation mentions only "ssh://". That said I prefer
"git+ssh://" to "ssh://" alone.
Second, IIRC Linus prefers scp-like syntax for SSH protocol, namely
"[user]@host:/path/to/repo", so perhaps that one should be used
instead.
>> Jakub was also talking about support in gitweb for specifying
>> the location of submodules. It would be nice if admins could
>> set this information, wherever it ends up getting stored.
>
> Hmm, this shouldn't be very hard to do if the support will get into
> gitweb. And adding the support to gitweb shouldn't be that hard either.
> :-) OTOH, it's not something that would get me terribly excited, so I
> guess I'll wait for the gitweb side.
The problem is that repo.or.cz needs support for that in gitweb, while
gitweb in turn needs support for that in git. This needs git consensus
on how to specify object database location (or just gitdir) for
submodules, to have later submodule support in gitweb.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2007-08-27 22:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-26 23:59 repo.or.cz wishes? Petr Baudis
2007-08-27 0:16 ` Sven Verdoolaege
2007-08-27 0:41 ` Petr Baudis
2007-08-27 18:23 ` Linus Torvalds
2007-08-27 18:58 ` Junio C Hamano
2007-08-27 19:09 ` Matthieu Moy
2007-08-27 20:05 ` Martin Mares
2007-08-27 21:27 ` Jing Xue
2007-08-27 22:27 ` Linus Torvalds
2007-08-27 22:58 ` Sam Vilain
2007-08-27 23:17 ` Linus Torvalds
2007-08-27 23:27 ` Jakub Narebski
2007-08-27 23:38 ` Linus Torvalds
2007-08-27 23:30 ` Sam Vilain
2007-08-27 23:34 ` Linus Torvalds
2007-08-27 23:16 ` Jakub Narebski
2007-08-27 21:58 ` Jakub Narebski [this message]
[not found] ` <20070828084939.GF1976MdfPADPa@greensroom.kotnet.org>
[not found] ` <200708282356.10605.jnareb@gmail.com>
2007-08-29 7:32 ` Sven Verdoolaege
2007-08-29 23:12 ` Jakub Narebski
2007-08-27 2:40 ` Sam Vilain
2007-08-27 8:35 ` Johannes Schindelin
[not found] ` <20070828041059.GK18160@spearce.org>
[not found] ` <20070828111913.GA31120@thunk.org>
[not found] ` <Pine.LNX.4.64.0708281230310.28586@racer.site>
[not found] ` <20070829042005.GT18160@spearce.org>
2007-08-29 9:54 ` Petr Baudis
[not found] ` <20070829041523.GS18160@spearce.org>
[not found] ` <7vr6lnszay.fsf@gitster.siamese.dyndns.org>
2007-08-29 9:58 ` Petr Baudis
2007-08-29 11:13 ` Theodore Tso
2007-08-31 21:09 ` Shawn O. Pearce
2007-08-29 17:11 ` Linus Torvalds
2007-09-01 2:58 ` Shawn O. Pearce
2007-08-27 19:49 ` Uwe Kleine-König
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=200708272358.43021.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
--cc=skimo@liacs.nl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).