[support] CVS/SVN best practices

Georg Rehfeld georg.rehfeld at gmx.de
Sun Jul 8 03:24:15 UTC 2007


Hi all,

I'm a Drupal newby, having read this list for 7 days now, before
attempting to post (but didn't search the archives thoroughly).

For a new Drupal site I use a Subversion (SVN) Repository, to be able
to track/revert changes to every modification I/we do to the site, e.g.
theme adaptions.

My current problem is: in many Drupal files (core and otherwise) there
is that special CVS/SVN string "$Id ... $".

When I now check in the original Drupal sources into _my_ SVN repository
all these $Id$ strings get replaced with my/our commit info.

In the first place this would be an (unwanted) fake: I/we ain't authors/
responsible for these files at all!

And, when synchronizing the local working copy with the life web server,
all these files show up as modified! Which is very annoying, because
_real_ changes are hidden amoung these fakes!

I would like to read, what's _your_ best practice to avoid that.

Thanks to all in advance, best regards,
Georg
-- 
   ___   ___
  | + | |__    Georg Rehfeld      Woltmanstr. 12     20097 Hamburg
  |_|_\ |___   georg.rehfeld.nospam at gmx.de    +49 (40) 23 53 27 10

               (Delete .nospam from mail address)


More information about the support mailing list