Re: Timestamp Issues

On 29 Nov 2004 Christopher Ness wrote:

> Ah, I get it! You have a tool that doesn't "deploy" files that haven't
> changed.

Yes. AN FTP client, in this case. It's a simple process.

> Do you _have_ to use that tool or can you do some scripting in SVN to
> deploy changes into production?

Well yes, but I'd rather not! I'm also used to simply observing the
timestamps (as in "well, I probably don't have to check there to see if
that's where the newly created problem is, because that file hasn't
changed since last July"). I shouldn't be reworking my whole work
environment to meet the needs of the VCS -- it should be a tool, not a
framework that defines the development setup (though these days, many
of the tools behave like wannbe frameworks! :-)).

> > It's too bad there's no way to select this as an option -- it appears
> > that it's going to make my use of Subversion a lot more difficult.
>
> That's one point of view. But with come creative juices (mostly coffee)
> you might be able to take out the middle man.

The FTP client isn't a "middle man" it's a tool appropriate for the
job. One of the things I like about Subversion is that it doesn't try
to be something more than a VCS -- but I wish (based on admittedly very
limited experience) that it didn't make quite so many assumptions about
how VCS users operate. Of course it has to make some -- I just want
the ones that don't work for *me* left out :-).

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