From: Matthew Summers <quantumsummers@gentoo.org>
To: gentoo-project@lists.gentoo.org, gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Use of git for site/proj/docs
Date: Sat, 26 May 2012 14:03:38 -0500 [thread overview]
Message-ID: <CAET+hMRfb2YC6Aomu5GXb5fedV5u+PGzvH2zPdk2-wMbW4QQUw@mail.gmail.com> (raw)
In-Reply-To: <20120526184732.GA4011@gentoo.org>
On Sat, May 26, 2012 at 1:47 PM, Sven Vermeulen <swift@gentoo.org> wrote:
> Hi guys,
>
> The gentoo CVS repository currently contains the sources for (at least) the
> following things:
>
> - the main gentoo site (through gentoo/xml/htdocs/main)
> - the gentoo documentation (gentoo/xml/htdocs/doc)
> - the gentoo project sites (gentoo/xml/htdocs/proj)
>
> A long time ago, there was talk about migrating it to git. From what I heard
> from Matthew, one of the things that might be interfering with this process
> is that the current gentoo/xml repository is too large, is that correct?
>
> I don't mind helping along here to get things forward.
>
> Wkr,
> Sven Vermeulen
>
It is not the size that matters, but the layout of the resulting repo
or repos. I know the Foundation has discussed having it's own repo.
There is also the news/gmn/gwn dir and so on.
How should these resultant repos be structured? Are we in a position
to retire some of the dirs in gentoo/ ?
--
Matthew W. Summers
Gentoo Foundation Inc.
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Summers <quantumsummers@gentoo.org>
To: gentoo-project@lists.gentoo.org, gentoo-project@gentoo.org
Subject: Re: [gentoo-project] Use of git for site/proj/docs
Date: Sat, 26 May 2012 14:03:38 -0500 [thread overview]
Message-ID: <CAET+hMRfb2YC6Aomu5GXb5fedV5u+PGzvH2zPdk2-wMbW4QQUw@mail.gmail.com> (raw)
Message-ID: <20120526190338.a7LDmtIP5uC2QmRHMhwPHGMWVesk8Ad34sqrYz9W-Io@z> (raw)
In-Reply-To: <20120526184732.GA4011@gentoo.org>
On Sat, May 26, 2012 at 1:47 PM, Sven Vermeulen <swift@gentoo.org> wrote:
> Hi guys,
>
> The gentoo CVS repository currently contains the sources for (at least) the
> following things:
>
> - the main gentoo site (through gentoo/xml/htdocs/main)
> - the gentoo documentation (gentoo/xml/htdocs/doc)
> - the gentoo project sites (gentoo/xml/htdocs/proj)
>
> A long time ago, there was talk about migrating it to git. From what I heard
> from Matthew, one of the things that might be interfering with this process
> is that the current gentoo/xml repository is too large, is that correct?
>
> I don't mind helping along here to get things forward.
>
> Wkr,
> Sven Vermeulen
>
It is not the size that matters, but the layout of the resulting repo
or repos. I know the Foundation has discussed having it's own repo.
There is also the news/gmn/gwn dir and so on.
How should these resultant repos be structured? Are we in a position
to retire some of the dirs in gentoo/ ?
--
Matthew W. Summers
Gentoo Foundation Inc.
next prev parent reply other threads:[~2012-05-26 21:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-26 18:47 [gentoo-project] Use of git for site/proj/docs Sven Vermeulen
2012-05-26 19:03 ` Matthew Summers [this message]
2012-05-26 19:03 ` Matthew Summers
[not found] ` <CAGfcS_kooiBz=pT0LnP=CHiOwNas-zo2VTUSKGn9dkAiN+9_+A@mail.gmail.com>
2012-05-26 22:14 ` Stuart Longland
2012-05-27 6:52 ` Michał Górny
2012-05-27 10:10 ` Sven Vermeulen
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=CAET+hMRfb2YC6Aomu5GXb5fedV5u+PGzvH2zPdk2-wMbW4QQUw@mail.gmail.com \
--to=quantumsummers@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
/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