All of 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: HG -> GIT migration
Date: Wed, 21 May 2008 00:12:28 +1000	[thread overview]
Message-ID: <1211292748.3811.7.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.61.0805201314190.1798@tm8103-a.perex-int.cz>

Jaraslay,

I tried tonight to run

git clone git@git.alsa-project.org:alsa-driver.git alsa-driver

I get the following output:
----------------------------------------------------------
ben@mythtv:~/ubuntu-kernel/alsa-git$ git clone
git@git.alsa-project.org:alsa-driver.git alsa-driver
Initialized empty Git repository
in /home/ben/ubuntu-kernel/alsa-git/alsa-driver/.git/
The authenticity of host 'git.alsa-project.org (212.20.107.51)' can't be
established.
RSA key fingerprint is da:f5:f8:5c:ed:a3:bc:78:a5:67:09:41:b6:a8:64:22.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'git.alsa-project.org,212.20.107.51' (RSA) to
the list of known hosts.
Password: 
Permissions on the password database may be too restrictive.
-----------------------------------------------------------
(I tried an empty password.)

So, can you please publish the RSA key fingerprint, and tell us how to
gain public read access?

I'd like to upload some changes later, do I need an account or something
to do that? Or just submit to ML? My changes *will* need review before
commit.

Thanks,
Ben Stanley.




On Tue, 2008-05-20 at 13:21 +0200, Jaroslav Kysela wrote:
> Hi all,
> 
> 	I finished migration from HG to GIT. All repositories are 
> converted and we have one "new" repository - alsa-kernel.git which is full 
> Linux 2.6 GIT tree. The old HG alsa-kernel repository was renamed to 
> alsa-kmirror - just to track our changes in continuous timeline for 
> releases and packaging. HG access to all repositories is closed now.
> 	More information can be obtained here:
> 
> http://www.alsa-project.org/main/index.php/GIT_Server
> 
> 						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-05-20 14:12 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20 11:21 HG -> GIT migration Jaroslav Kysela
2008-05-20 14:12 ` Ben Stanley [this message]
2008-05-20 14:24   ` Jaroslav Kysela
2008-05-21  2:30 ` Eliot Blennerhassett
2008-05-21  6:09   ` Jaroslav Kysela
2008-05-21 10:28     ` Takashi Iwai
2008-05-21 12:30       ` Rene Herman
2008-05-21 12:37         ` Takashi Iwai
2008-05-21 13:04           ` Rene Herman
2008-05-21 13:04             ` [alsa-devel] " Rene Herman
2008-05-21 13:48             ` Jaroslav Kysela
2008-05-21 14:40               ` Rene Herman
2008-05-21 14:40                 ` [alsa-devel] " Rene Herman
2008-05-21 14:52                 ` Takashi Iwai
2008-05-21 14:52                   ` [alsa-devel] " Takashi Iwai
2008-05-21 15:29                   ` Rene Herman
2008-05-21 15:29                     ` [alsa-devel] " Rene Herman
2008-05-22  1:24                     ` Stephen Rothwell
2008-05-22 20:43                       ` Rene Herman
2008-05-22 20:43                         ` [alsa-devel] " Rene Herman
2008-05-22 23:40                         ` Stephen Rothwell
2008-05-22 23:40                           ` [alsa-devel] " Stephen Rothwell
2008-05-21 14:47             ` Takashi Iwai
2008-05-21 14:47               ` [alsa-devel] " Takashi Iwai
2008-05-21 15:40               ` Rene Herman
2008-05-21 15:40                 ` [alsa-devel] " Rene Herman
2008-05-21 16:02                 ` Takashi Iwai
2008-05-21 16:02                   ` [alsa-devel] " Takashi Iwai
2008-05-21 16:16                   ` Linus Torvalds
2008-05-21 16:51                     ` Takashi Iwai
2008-05-21 16:51                       ` [alsa-devel] " Takashi Iwai
2008-05-21 17:07                       ` Tobin Davis
2008-05-21 17:19                         ` Jaroslav Kysela
2008-05-21 17:22                         ` Rene Herman
2008-05-21 17:43                       ` [alsa-devel] " Linus Torvalds
2008-05-21 18:11                         ` Linus Torvalds
2008-05-21 18:11                           ` [alsa-devel] " Linus Torvalds
2008-05-21 18:25                           ` david
2008-05-21 18:39                             ` Linus Torvalds
2008-05-21 18:39                               ` [alsa-devel] " Linus Torvalds
2008-05-21 18:49                             ` Takashi Iwai
2008-05-21 18:49                               ` [alsa-devel] " Takashi Iwai
2008-05-21 18:47                         ` Takashi Iwai
2008-05-21 18:47                           ` [alsa-devel] " Takashi Iwai
2008-05-21 19:02                           ` Linus Torvalds
2008-05-21 19:02                             ` [alsa-devel] " Linus Torvalds
2008-05-21 21:08                             ` Takashi Iwai
2008-05-21 21:08                               ` [alsa-devel] " Takashi Iwai
2008-05-22 14:23               ` Dmitry Torokhov
2008-05-21 22:16     ` Eliot Blennerhassett
2008-05-23  2:31       ` Ben Stanley
2008-05-23  6:38         ` Jaroslav Kysela

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=1211292748.3811.7.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 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.