Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Sender: trawick@rdu88-250-166.nc.rr.com
To: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
Cc: dev@apr.apache.org
Subject: Re: [PATCH] Adding an apr_utime() function
References: <OF823E8EE0.0D78E184-ON86256B7C.00654E39@rchland.ibm.com>
	<OF823E8EE0.0D78E184-ON86256B7C.00654E39@rchland.ibm.com>
	<5.1.0.14.2.20020314142259.02351680@localhost>
From: Jeff Trawick <trawick@attglobal.net>
Date: 14 Mar 2002 17:22:50 -0500
In-Reply-To: <5.1.0.14.2.20020314142259.02351680@localhost>
Message-ID: <m3elimeqmd.fsf@rdu88-250-166.nc.rr.com>
Lines: 22
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

"William A. Rowe, Jr." <wrowe@rowe-clan.net> writes:

> Before anyone even _considers_ polluting the API [which would
> raise an instant veto from me] we have to finally address the create
> time issue on non-Unix.  Then we can get such a patch committed
> to fit this resolution of this issue..
> 
> Unix has ctime, mtime and atime.  How often will we change all three
> at once, or do we want to change a single requested time-at-a-time?

That is a key question.  I wish I knew the answer :)  Rob, what is
your use case by the way?  Not that it is the answer for everybody,
but I'm curious.

The change-one-time per call handles your issues nicely.  It might be
nice to have a flag that says to just set everything to the one time
so that we don't waste a syscall trying to preserve the times we don't
think we're supposed to modify.

-- 
Jeff Trawick | trawick@attglobal.net
Born in Roswell... married an alien...