New user, file timestamp question.

[Mark Swann <ms...@echo-inc.com>]

(Win2000)
I downloaded Subversion 0.20.1,
installed it,
created a new repository,
imported some files and
checked out the files into a new workspace.

Why are the time stamps in the workspace files different than the time
stamps in the original files?
Can this be corrected? Is it corrected in a later revision? The date of last
modification is as important as the contents of the file.


Mark Swann
ECHO, Inc.
---------------------
* May the Form be with you.
* Beware of the dark side of the Form.
* Live by the Form, Die by the Form.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: New user, file timestamp question.

[cm...@collab.net]

Peter Poeml <po...@suse.de> writes:

> > We've talked about adding an svn:original-date property to at least
> > remember the imported date, but I can't remember how that conversation
> > turned out.
> 
> Even if preserving timestamps across an import is not supported, as far
> as I can see preverving them across a checkout doesn't work either. But
> the latter *does* work with CVS.
> 
> On a related issue, what about file permissions? I run a repository of a
> lot of files with mode 600, and I noticed that upon checkout all files
> are created with the current umask (e.g. world readable). (It is not a
> build system.). 
> 
> Only an "executable" flag would be retained, as it looks.
> 
> Is there no way to do retain file timestamps or permissions?

The short answer:  no.

The long answer:  don't get me started on what a Version Control
system is and isn't.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: New user, file timestamp question.

[Peter Poeml <po...@suse.de>]

On Thu, Apr 17, 2003 at 02:54:09PM -0400, Greg Hudson wrote:
> On Thu, 2003-04-17 at 00:54, Rob Kramer wrote:
> > I asked this a few days ago, but didn't get an anwer yet. I think it is 
> > because perhaps it is a Dumb Question. :)
> 
> It's not a dumb question, but it's a problem of conflicting constraints:
> 
>   * There are reasons to want to preserve timestamps across an import
> and checkout, e.g. if you're checking in generated files and you want
> your build system to know that it doesn't have to regenerate those
> files.
> 
>   * On the other hand, if a checkout or update munges timestamps, you
> run the risk of fooling a build system into thinking a file hasn't been
> modified when it has.  Consider:
> 
>   svn co project-url wc
>   cd wc; make
>   svn update -r oldrev file
>   make
> 
>   * And, of course, we want to keep our code simple, particularly inside
> libsvn_wc where things are already a bit messy.  So having a lot of
> dials and knobs isn't great either.
> 
> We've talked about adding an svn:original-date property to at least
> remember the imported date, but I can't remember how that conversation
> turned out.

Even if preserving timestamps across an import is not supported, as far
as I can see preverving them across a checkout doesn't work either. But
the latter *does* work with CVS.

On a related issue, what about file permissions? I run a repository of a
lot of files with mode 600, and I noticed that upon checkout all files
are created with the current umask (e.g. world readable). (It is not a
build system.). 

Only an "executable" flag would be retained, as it looks.

Is there no way to do retain file timestamps or permissions?

Peter

-- 
Thought is limitation. Free your mind.

Re: New user, file timestamp question.

[Greg Hudson <gh...@MIT.EDU>]

On Thu, 2003-04-17 at 00:54, Rob Kramer wrote:
> I asked this a few days ago, but didn't get an anwer yet. I think it is 
> because perhaps it is a Dumb Question. :)

It's not a dumb question, but it's a problem of conflicting constraints:

  * There are reasons to want to preserve timestamps across an import
and checkout, e.g. if you're checking in generated files and you want
your build system to know that it doesn't have to regenerate those
files.

  * On the other hand, if a checkout or update munges timestamps, you
run the risk of fooling a build system into thinking a file hasn't been
modified when it has.  Consider:

  svn co project-url wc
  cd wc; make
  svn update -r oldrev file
  make

  * And, of course, we want to keep our code simple, particularly inside
libsvn_wc where things are already a bit messy.  So having a lot of
dials and knobs isn't great either.

We've talked about adding an svn:original-date property to at least
remember the imported date, but I can't remember how that conversation
turned out.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

RE: New user, file timestamp question.

[Sander Striker <st...@apache.org>]

> From: Rob Kramer [mailto:rob@infologic.com.sg]
> Sent: Thursday, April 17, 2003 6:55 AM

> Hello Mark,
> 
> On Thursday 17 April 2003 06:39, Mark Swann wrote:
> > Why are the time stamps in the workspace files different than the time
> > stamps in the original files?
> > Can this be corrected? Is it corrected in a later revision? The date of
> > last modification is as important as the contents of the file.
> 
> I asked this a few days ago, but didn't get an anwer yet. I think it is 
> because perhaps it is a Dumb Question. :)
> 
> I was thinking about my problem a bit more (importing some really old versions 
> of a project to create a SVN history for it), but don't think it would be 
> possible at all. You'd have to import files that are older than the current 
> repository, so you'd have to change the repository in the past. I can imagine 
> that would be a nasty thing to do..
> 
> Losing file timestamps is an obstacle in getting my company to switch to a 
> source version control system - everybody uses file dates to track the 
> versions here (and it gets messy sometimes).

Ouch!  That is just plain nasty.  It will all fall down when someone sends
another person an older file which gets a new timestamp...

Sander

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: New user, file timestamp question.

[Rob Kramer <ro...@infologic.com.sg>]

Hello Mark,

On Thursday 17 April 2003 06:39, Mark Swann wrote:
> Why are the time stamps in the workspace files different than the time
> stamps in the original files?
> Can this be corrected? Is it corrected in a later revision? The date of
> last modification is as important as the contents of the file.

I asked this a few days ago, but didn't get an anwer yet. I think it is 
because perhaps it is a Dumb Question. :)

I was thinking about my problem a bit more (importing some really old versions 
of a project to create a SVN history for it), but don't think it would be 
possible at all. You'd have to import files that are older than the current 
repository, so you'd have to change the repository in the past. I can imagine 
that would be a nasty thing to do..

Losing file timestamps is an obstacle in getting my company to switch to a 
source version control system - everybody uses file dates to track the 
versions here (and it gets messy sometimes). I use CVS for my projects and 
never use timestamps to track history. Will switch to SVN one of these days, 
when I'm convinced cvs2svn works fine. Maybe it already does :)

Cheers,

   Rob


-- 
main() {fork(); main();}


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org