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

Re: [PATCH] Update HACKING: Mutual respect / Evaluate the code, not the coder.

From: Jack Repenning <jrepenning_at_collab.net>
Date: Thu, 16 Apr 2009 11:35:07 -0700

On Apr 16, 2009, at 3:34 AM, Arfrever Frehtes Taifersar Arahesis wrote:

> The attachment was also broken.
>
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1696155
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1698044
> http://svn.haxx.se/dev/archive-2009-04/0398.shtml
> http://svn.haxx.se/dev/archive-2009-04/0400.shtml

I see "the attachment created by our butt-head mailer, from text that
was originally just the message body, is broken."

I do not see "an attachment provided by the original sender is broken."

Are you seeing something different?

The current state and plan, as we understand it, is:

1. attachments provided by the originator are not munged
2. code review can be performed, if necessary by attaching the patch
rather than in-lining it
3. the fix to un-butt-head our ML is scheduled for the next _release_,
not _patch_ or _hot-fix_, because of the above two mitigators

I'm trying to explain the current state as clearly as possible; I'm
not arguing that the current state is right (God forbid!), or even
optimal; just explaining what it is. If the mitigators don't actually
happen, I want to know about that. If you think the mitigators aren't
good enough, I want to know about that as well.

-==-
Jack Repenning
Chief Technology Officer
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
office: +1 650.228.2562
mobile: +1 408.835.8090
raindance: +1 877.326.2337, x844.7461
aim: jackrepenning
skype: jackrepenning
twitter: http://twitter.com/jrep

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1752317
Received on 2009-04-16 20:35:23 CEST

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.