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

Re: RFC: change to HACKING guidelines on log messages

From: <kfogel_at_collab.net>
Date: 2004-10-11 19:10:06 CEST

Grzegorz Adam Hankiewicz <gradha@titanium.sabren.com> writes:
> This is something I had not noticed before, and couldn't find it in
> HACKING. Is it a convention you have for every kind of text document?

Yes, though not strictly enforced. The two-spaces rule helps those of
us who use sentence-motion commands in our editors.

> > Want to commit it?
> I thought my access would be restricted to doc/translations/spanish/*.

Well, if someone with commit access to area A approves you to make a
commit in area A, then you can make that commit in area A :-). Just
mention the name of the committer who approved it, in your log message.

The long-term goal is that partial committers can gradually expand
their areas. For example, if you post 3 patches that fix typos or
other problems in documentation, and they all get approved for commit,
then eventually someone will propose (privately, among the other full
committers) that your commit rights be expanded to include all
documentation. No one will disagree, and so your access will be

Thus, we're "carefully loose" about the restrictions.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 11 20:59:02 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.