public inbox for [email protected]  

help / color / mirror / Atom feed

From: Alexey Borzov <[email protected]>
To: Dave Page <[email protected]>
Cc: [email protected]
Subject: Re: Update on 'portal' changes
Date: Mon, 08 Mar 2004 20:11:25 +0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Hi!

Dave Page wrote:
>>Speaking of which, what is the real reason for keeping the 
>>current website and the "next-generation" one in one project?
>>
>>Maybe a better approach would be to register a separate 
>>project for the next-generation website (I think this was 
>>already proposed here)?
> 
> Because the project is for all the websites, not just the one you are
> working on.

OK, let's paraphrase: what is the reason for having one project for all websites 
instead of one project per website? I got the impression that *different* 
developers work on different websites...

> We *have* created a separate CVS module which should be more than enough
> segregation.

Can CVS write access be given for this module only?

view thread (28+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Update on 'portal' changes
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox