Hi folks
I'd like to discuss structure of the repositories we create on git.linaro.org for interaction with upstreams using git (e.g. kernel and u-boot).
I think we should have two layouts: - /$person/$project/$topic repos for personal repositories, - /$project/$topic repos for canonical repositories, such as team repos
For instance, /jcrigby/u-boot/for-upstream.git or /linaro-kernel/linux/arm-next.git.
What do you folks think?
Thanks!
On Fri, Jun 11, 2010 at 12:23 PM, Loïc Minier loic.minier@linaro.orgwrote:
Hi folksI'd like to discuss structure of the repositories we create on git.linaro.org for interaction with upstreams using git (e.g. kernel and u-boot).
I think we should have two layouts:
- /$person/$project/$topic repos for personal repositories,
- /$project/$topic repos for canonical repositories, such as team repos
For instance, /jcrigby/u-boot/for-upstream.git or /linaro-kernel/linux/arm-next.git.
What do you folks think?
Thanks!
Too over-specified IMO. If you just want to keep the team repos separate from the personal development repos, let them be under personal/ directory. People can then use whatever naming scheme that makes sense.
So you won't have so many personal git trees like on kernel.ubuntu.com/git(they'll all be hidden away in the personal/ folder)
Regards, Amit
On Fri, Jun 11, 2010, Amit Kucheria wrote:
Too over-specified IMO. If you just want to keep the team repos separate from the personal development repos, let them be under personal/ directory. People can then use whatever naming scheme that makes sense.
I do want the top-level to be specified in someway, either it could be personal/$nick/whatever, or directly $nick/whatever. The rest is more a recommendation, but in practice people are free to make exceptions.
So you won't have so many personal git trees like on kernel.ubuntu.com/git(they'll all be hidden away in the personal/ folder)
Is it an issue when finding shared repos that you think we should try hiding personal trees?
On Sat, Jun 12, 2010 at 11:27 AM, Loïc Minier loic.minier@linaro.orgwrote:
On Fri, Jun 11, 2010, Amit Kucheria wrote:
Too over-specified IMO. If you just want to keep the team repos separate from the personal development repos, let them be under personal/
directory.
People can then use whatever naming scheme that makes sense.
I do want the top-level to be specified in someway, either it could be personal/$nick/whatever, or directly $nick/whatever. The rest is more a recommendation, but in practice people are free to make exceptions.
So you won't have so many personal git trees like on kernel.ubuntu.com/git(they'll http://kernel.ubuntu.com/git%28they%27llall be hidden away in the personal/ folder)
Is it an issue when finding shared repos that you think we should try hiding personal trees?
Most of the time, personal trees only contain temporary stuff, a staging tree before things move to official tree.
And keeping it hidden away under a personal/ directory makes clear the official repositories.
Texas Instruments France SA, 821 Avenue Jack Kilby, 06270 Villeneuve Loubet. 036 420 040 R.C.S Antibes. Capital de EUR 753.920
-----Original Message-----
From: linaro-dev-bounces@lists.linaro.org [mailto:linaro-dev- bounces@lists.linaro.org] On Behalf Of Loïc Minier Sent: Saturday, June 12, 2010 11:27 AM To: linaro-dev@lists.linaro.org Subject: Re: [Linaro-dev] git.linaro.org repos structure
On Fri, Jun 11, 2010, Amit Kucheria wrote:
Too over-specified IMO. If you just want to keep the team repos separate from the personal development repos, let them be under personal/
directory.
People can then use whatever naming scheme that makes sense.
I do want the top-level to be specified in someway, either it could be personal/$nick/whatever, or directly $nick/whatever. The rest is more a recommendation, but in practice people are free to make exceptions.
So you won't have so many personal git trees like on kernel.ubuntu.com/git(they'll all be hidden away in the personal/ folder)
Is it an issue when finding shared repos that you think we should try hiding personal trees?
[nd] how about something like this: http://arago-project.org/git/. The main page is for release trees, then you have a different area for personal/project trees that do not pollute the main area...
-- Loïc Minier
Linaro-dev mailing list Linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
On Mon, Jun 14, 2010, Dechesne, Nicolas wrote:
[nd] how about something like this: http://arago-project.org/git/. The main page is for release trees, then you have a different area for personal/project trees that do not pollute the main area...
I have taken action to check with IS what we can get, what you point at is a good example; thanks
On Mon, Jun 14, 2010, Dechesne, Nicolas wrote:
[nd] how about something like this: http://arago-project.org/git/. The main page is for release trees, then you have a different area for personal/project trees that do not pollute the main area...
IS asked whether we had a specific config for gitweb/apache2 in mind, and whether we could simply provide the config we'd like to use; would someone be able to provide that or should I research it?
Thanks
-
Amit Kucheria -
Dechesne, Nicolas -
Loïc Minier