Re: [B.A.T.M.A.N.] RFC: Migration to a new git server backend

[Sven Eckelmann <sven@narfation.org>]

[-- Attachment #1: Type: text/plain, Size: 1636 bytes --]

Hi,

I was just asked whether the repo urls will change. I can only say for sure 
that the administration URL url will be changed. But to the rest...

On Sunday 22 July 2012 01:43:25 Sven Eckelmann wrote:
> Now the question is: Do we want to use this feature or not. We had following
> ideas:
> 
> 1. 1 repository per project
> 
>    use only one repo for each project (batman-adv, batctl, batmand, ...) and
> use branch namespaces for individual users:
>    * master, next, maint for the main stuff
>    * ordex/ (for example ordex/dat), hundeboll/, ... for users
>    * tags only for release team

I would like not to change the repo URL for the main repository. The other 
repositories would disappear and therefore their URLs get changed.

> 2. 2 repositories per project
> 
>    use one official repo for each project (batman-adv, batctl, batmand, ...)
> and one for other people
>    * master, next, maint in both repos (synced from the main one)
>    * ordex/ (for example ordex/dat), hundeboll/, ... for users in the second
> repo
>    * tags in both repositories allowed (but in the second repo only with
>      user prefix)

The main repo would have the same URL as before. The other URLs get mapped to 
the second user repo.

> 3. 1+x repositories per project
> 
>    Keep everything like now
>    * master, next, maint for the main stuff
>    * each user has his own copy of the main repo in his user folder
>    * tags can freely commit in his own repo

We would have the same URLs for the repos as before.

Of course, if you have any other ideas about the folder structure then please 
discuss it now.

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]