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

Re: Incoherent patch guidelines

From: <kfogel_at_collab.net>
Date: 2004-09-20 20:43:47 CEST

Grzegorz Adam Hankiewicz <gradha@titanium.sabren.com> writes:
> The patch guidelines in the HACKING file state that the recommended
> way to send patches is included in the body of the message. On the
> other hand, http://subversion.tigris.org/mailing-list-guidelines.html
> states that the best is to attach them. What will it be then?
> About writing log messages, it is unclear how to deal with patches
> which deal with only a single file. Specifying it in the log
> message itself seems quite useless because the generated patch
> already contains a path reference to the file being modified. IOW,
> the guideline illustrates the complex example and fails to show a
> basic version for one line patches.

I've fixed it in r11057.

> Please don't send me private copies of your public answers. Thanks.

And, I've carefully not CC'd you on this public answer -- sorry for
the other time.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 20 22:27:51 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.