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

Re: Best Practices

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-08-08 22:37:12 CEST

Josef Wolf <jw@raven.inka.de> writes:
> Hmmm, I don't like (1) because it is too smattering. I neither like (2)
> because it describes only a special case (changing whitespace) of the
> (more general) coding-style-issue (see above). While "diff -w" and
> "patch -l" can help you out with changing whitespace to some degree,
> I know of no good solution for changing style from e.g. GNU to K+R or
> vice-versa. Therefore I feel that it is much more important to warn
> of changing style than just changing whitespace.

Good point. After we commit Scott's material (as soon as I climb out
of my coding stack), maybe you/him/both can massage it accordingly.

> I think it might be a good idea to make this document a
> plain-text-file. This way people could just copy+paste the parts
> they think their project would benefit of into their HACKING file.
> Such a decision would imply that it should _not_ go into the
> handbook, since the handbook is not plan-text. It could be even
> splitted into a texinfo-part for the appendix and a plain-text-part
> for copy+paste.

I think you can generate plain text from the handbook.

> An issue with such a document and discussions about it is that it
> could provoke religious wars. I am not sure whether it is always
> possible to avoid such wars. OTOH I think we should definitely keep
> such wars out of the developers list. If we want to continue this
> discussion, it probably should move to the user's mailing-list?
> Isn't it time to activate the user's list now that Alpha is out?

Not yet, I think. We still want feedback to be visible to everyone.

Anyway, religious wars are just as counterproductive on the users list
as they are on the dev list. If the document starts provoking such
wars, we can deal with it then. Thus far, it hasn't. (Earlier
proposals to create a much *broader* document did, but we've
fortunately settled on a Subversion-specific document).

> While we are at the changing-whitespace-topic: IMHO "svn switch" and
> "svn update" should get an option like --ignore-whitespace because
> they often run diff/patch internally to do the merges... Hmmm, maybe
> giving them something like --tabify and --untabify could be a good
> idea, too?

I haven't given it much thought, and frankly can't right now. Maybe
someone else can...

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 8 22:53:20 2002

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.