[dev] VCS Keywords in License Headers

After the switch to Subversion, the license headers in all the OOo source files (taken from the templates and ) still contain $RCSfile$ and $Revision$ keywords with old value

Re: [dev] VCS Keywords in License Headers

Hi +1 for the proposal Heiner Stephan Bergmann wrote: > After the switch to Subversion, the license headers in all the OOo > source files (taken from the templates > and > ) s

Re: [dev] VCS Keywords in License Headers

> +1 for the proposal +1 Is this something which can/should be done by release engineering, for instance with the switch from m32 to m33, globally? Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffi

Re: [dev] VCS Keywords in License Headers

Hi Frank, Frank Schönheit - Sun Microsystems Germany wrote: >> +1 for the proposal > > +1 > > Is this something which can/should be done by release engineering, for > instance with the switch from m32 to m33, globally? Yes, this can (and should) be done by RE, if we decide drop the VCS keywords

Re: [dev] VCS Keywords in License Headers

Hi Heiner, > Yes, this can (and should) be done by RE, if we decide drop the VCS > keywords. Most probably not m33, but at some time in the near future. would be good. > Another huge change which could be done in the same milestone is to > convert tabs to 4 spaces, something I know Kendy and som

Re: [dev] VCS Keywords in License Headers

Frank Schönheit - Sun Microsystems Germany wrote: > Hi Heiner, > >> Yes, this can (and should) be done by RE, if we decide drop the VCS >> keywords. Most probably not m33, but at some time in the near future. > > would be good. > >> Another huge change which could be done in the same milestone i

Re: [dev] VCS Keywords in License Headers

Hi Heiner, > 'svn merge -x -b' is your friend ... You mean ... I really should go reading this Handbuch? :) > Could be done, and the earlier the better I guess. As long as we still have CVS-based CWS'es, which need to be migrated ... not sure. Finally, migration will probably usually happen by

Re: [dev] VCS Keywords in License Headers

Frank Schönheit - Sun Microsystems Germany wrote: > Hi Heiner, > >> 'svn merge -x -b' is your friend ... > > You mean ... I really should go reading this Handbuch? :) > >> Could be done, and the earlier the better I guess. > > As long as we still have CVS-based CWS'es, which need to be migrated

Re: [dev] VCS Keywords in License Headers

Hi Heiner, >> As long as we still have CVS-based CWS'es, which need to be migrated ... >> not sure. Finally, migration will probably usually happen by "create a >> CWS in SVN, based on the latest milestone, and *patch* in the changes of >> the CVS-CWS". In this case, "svn merge" is of no help. Ins

Re: [dev] VCS Keywords in License Headers

On 01.10.08 12:08, Jens-Heiner Rechtien wrote: Hi Frank, Frank Schönheit - Sun Microsystems Germany wrote: +1 for the proposal +1 Is this something which can/should be done by release engineering, for instance with the switch from m32 to m33, globally? Yes, this can (and should) be done by

Re: [dev] VCS Keywords in License Headers

On Mon, 2008-10-06 at 09:20 +0200, Stephan Bergmann wrote: > Regarding the tab conversion, I guess such a one-time conversion won't > help much unless we could ensure that no new tabs get introduced with > new commits. I've long stuck /* vi:set tabstop=4 shiftwidth=4 expandtab: */ at the bott

Re: [dev] VCS Keywords in License Headers

Hi, there seems to be an agreement that VCS keywords do not make any sense anymore and should be removed. Hamburg RE will take care of this. The tabs converted to spaces issue seems somewhat more controversial. At least we have to move it out of the migration phase. I've played with the idea of a

[dev] SVN Hooks for formatting (was: Re: [dev] VCS Keywords in License Headers)

On 10/06/08 09:57, Caolán McNamara wrote: And subversion (like cvs) has a precommit hook that can e.g. reject files with tabs in them. e.g. http://wordaligned.org/articles/a-subversion-pre-commit-hook +1 I would really appreciate such a hook, I just didnt dare to propose this yet. Have Fu