Quoting Michael Renzmann <mrenzmann <at> madwifi.org>:

> Pavel Roskin wrote:
>> We could run the git repository on the madwifi server instead, and
>> that would give it a more official status.  Still, we can require that
>> the git repository remains strictly a mirror.
>
> I tend to keeping everything that's related to MadWifi on madwifi.org, if
> possible, so that people don't need to look around at different places.
> Thus I'd vote for run the git repository on madwifi.org.
>
> Is there any special requirement that must be met on the server for this?
> Or any "nice to have" things that would make life of those working with
> the repository easier?

It would be nice to have http access to the repository.  Please see  
this file in the git sources:  
Documentation/howto/setup-git-server-over-http.txt

Of course, the native git protocol should be enabled too.

It would be nice to have the latest released version of git, just to  
avoid known problems.  The last version is currently 1.5.6.4 and can  
be downloaded from
http://git.or.cz/

>> I don't know if anyone needs a public personal repository.  Such
>> repositories could be hosted elsewhere, including repo.or.cz.
>
> Same here, just tell me what is required to allow hosting such personal
> repositories and I'll try to make it happen. As long as the repository is
> related to the madwifi.org project, at least :)

I believe ssh access with be required to run git over ssh.

My biggest concern is whether we can import svn branches as git  
branches.  We changed the repository structure in the past, so it may  
interfere with the import.  If it doesn't work, I'm not even sure we  
want an official git repository, as it will either miss the branches  
or is will force users to download all branches.  And the worst thing  
is that git won't be able to merge anything.

We could use an intermediate svn repository that would use the current  
layout for historic revisions (svk may help to speed it up).  We could  
patch git-svn to guess branch locations.  We could interpret old and  
new paths as different branches.  Or we could start the git history  
from the point where the layout changed, but that would lose useful  
history.

I see that git-svn has an option --follow-parent, which could help.   
But I'm afraid we'll still need to patch git-svn to have the complete  
history.  Or we'll need an svn mirror with straightened history.

That's the real issue.  Once we deal with it, we can set up the  
repository anywhere.  I don't think anyone has a git mirror with the  
full history and correct branches.  I'd like to be proven wrong.

-- 
Regards,
Pavel Roskin

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/