Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Stanley <Ben.Stanley@exemail.com.au>
To: Jaroslav Kysela <perex@perex.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: GIT repo (connection refused)
Date: Fri, 04 Jul 2008 06:53:51 +1000	[thread overview]
Message-ID: <1215118431.30056.194.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.61.0807011521070.20581@tm8103-a.perex-int.cz>

Jaroslav,

When I try to edit the Occasional Developers section on the page
http://www.alsa-project.org/main/index.php/GIT_Server
I am told:

This page has been locked to prevent editing.

Ben.

On Tue, 2008-07-01 at 15:22 +0200, Jaroslav Kysela wrote:
> On Tue, 1 Jul 2008, Ben Stanley wrote:
> 
> > 
> > Check if you are behind a firewall that blocks the git protocol on port
> > 9418. The http version is there for people who are behind such a
> > firewall.
> > 
> > That being said, the http version should be documented on the git page,
> > rather than just on the mailing list at
> > http://thread.gmane.org/gmane.linux.alsa.devel/53959/focus=54060
> > (Nudge to Jaroslav)
> 
> HTTP access is on http://www.alsa-project.org/main/index.php/GIT_Server 
> already, but not in Occasional Developers section. Just add this 
> information there. Everybody registered can modify this page.
> 
> 					Jaroslav
> 
> -----
> Jaroslav Kysela <perex@perex.cz>
> Linux Kernel Sound Maintainer
> ALSA Project, Red Hat, Inc.
> 
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2008-07-03 20:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01  9:18 GIT repo (connection refused) Aldrin Martoq
2008-07-01 13:19 ` Ben Stanley
2008-07-01 13:22   ` Jaroslav Kysela
2008-07-03 20:53     ` Ben Stanley [this message]
2008-07-03 21:33       ` Ben Stanley

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=1215118431.30056.194.camel@localhost \
    --to=ben.stanley@exemail.com.au \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@perex.cz \
    /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