[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: PATCH: $Header$ handling

From: Krebs, Steven <steven.krebs_at_intel.com>
Date: 2004-07-21 19:41:59 CEST

Alex,

I am grateful for the patch... I am getting ready to covert my PVCS VM
repo over to Subversion, and I was going to s/$Header$/$Id$\n$HeadURL$/
in all of my source code and then go update our coding standards (that
require our developers to put $Header$ at the top of each new source
file) and then explain to my few dozen developers why they have to
change their process... But, with this patch, I won't have too.
Thanks much. Sometimes the littlest things have a bigger impact than
you expect. (Please accept John's advice to follow the standards in
HACKING so this patch can be considered for adoption, thanks. )

Steve Krebs
Validation Tools - ITP Team
Intel Corporation

-----Original Message-----
From: John Peacock
Sent: Wednesday, July 21, 2004 6:52 AM
To: Alexander L. Belikoff
Cc: dev@subversion.tigris.org
Subject: Re: PATCH: $Header$ handling

Alexander L. Belikoff wrote:
> Attached (and included) is a patch implementing the RCS $Header$
keyword. A
> lot of people have been asking for this and quite a lot of people use
it a
> lot.

I've been closely watching the keyword topic since I joined the list
(and have a patch in process to change the keyword handling completely),

and I have to say that $Header$ has not been that highly demanded (no
offense intended). As I suggested in your original thread, the use of
$Header$ to create reports is trying to map CVS methodology to
Subversion.

That being said, please read HACKING and include a log message in the
project style so that this patch can be considered for adoption.

John

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 21 19:43:09 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.