Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 4 Jul 2001 13:51:54 -0700
From: Justin Erenkrantz <jerenkrantz@ebuilt.com>
To: David Reid <dreid@jetnet.co.uk>
Cc: apr dev <dev@apr.apache.org>
Subject: Re: pools code
Message-ID: <20010704135154.S7717@ebuilt.com>
References: <3B437DF8.33F7027D@jetnet.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <3B437DF8.33F7027D@jetnet.co.uk>;
 from dreid@jetnet.co.uk on Wed, Jul 04, 2001 at 09:35:05PM +0100

On Wed, Jul 04, 2001 at 09:35:05PM +0100, David Reid wrote:
> Anyone have objections to moving the apr_pools.c file into the
> memory/unix directory?

No objections here, but I wouldn't worry about the history.
Just note that the file originally came from lib/apr_pools.c.
If you want to see the history from when it was lib/apr_pools.c,
go there.  =)  Moving the RCS file is generally a bad thing.

So, IMHO, prolly better to do:
mv lib/apr_pools.c memory/unix/apr_pools.c
(clean up the Makefile.in, regenerate, test, etc.)
cvs delete lib/apr_pools.c
cvs add memory/unix/apr_pools.c
cvs commit

My $.02.  -- justin