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

Re: Post processing of check out and pre processing of commits

From: mep <res00fr1_at_gmail.com>
Date: 2007-11-12 23:29:51 CET


Thanks for your response.

I overlooked the importance of keeping the local stored copy the same
as the server. This complicates getting it done automatically. Doing
it in the context of the editor makes a lot of sense.

On Nov 12, 2007 1:31 PM, John Peacock <john.peacock@havurah-software.org> wrote:
> mep wrote:
> > Is there a built in mechanism for inserting a "pretty printer"?
> No, but you could write a wrapper to do it for you. The issue is that
> you should not (read MUST NOT) change the transaction in progress, so
> that the file as stored on the server is always the same as the file
> stored on the client.
> If you *really* want to do this, I would create a [insert your favorite
> scripting language here] script called `edit` which would transform the
> file on disk using your personal style, call up your editor, then
> transform the file into the company-standard style on the after the
> editor closes.
> Of course, there is something to be said for:
> a) learning to use your company's standard style;
Of course, I've done that. For the first time in my programming life,
I've been criticized for having too many comments and too much white

> b) convincing your boss that your style is better. ;-)
This must be done very diplomatically since I'm the new kid on the
block. And I would have to get it through my boss all the way up to
one of the founders of the company. Hence the less problematic
approach to get around the issue.


Sure did, my path is well defined and I can continue by working on the
editor's scripts.

> John

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 12 23:30:16 2007

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

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