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

Re: attachments...

From: Greg Stein <gstein_at_gmail.com>
Date: Tue, 16 Dec 2008 02:26:27 -0800

On Tue, Dec 16, 2008 at 00:30, Branko Cibej <brane_at_xbc.nu> wrote:
> Stefan Sperling wrote:
>> On Mon, Dec 15, 2008 at 12:06:23PM -0600, Hyrum K. Wright wrote:
>>
>>> (Let's hope tigris doesn't munge the attachment this time...)
>>
>> And it did it again!
>>
>> I'm starting to wonder what the mythical 3 engineers are doing
>> these days :)
>
> You said it ... they're being mythical.

From IRC:

jackr: We actually have two attachments-related changes; do you care
about both? Prolly.
jackr: On the matter of "attachments sometimes disappearing," this has
been scheduled for the next release ("Indus"), target end of 1Q09
jackr: On the matter of "long plain messages being turned into
attachments," this is still in the support team; they suspect they
know the fix but are at the point of verification

If the first means "Hyrum's attached patch was dropped, and sub'd with
the message body", the end of Q1 is NOT acceptable.

If it means something else, then okay. But I'm not familiar with that
bug, so some further explanation would be handy, and a third bug
should be filed for Hyrum's problem from earlier today.

The second bug: where large patches, or large commit messages become
unusable email messages? Yah. That would be good to have fixed. I'm
not sure why that one is difficult. Somewhere in the code, there is a
decision point on what "message too big" means, so it should just get
commented out and redployed to the site. Are there other, systemic
problems with that? Well, possibly, but a little clarity would be
helpful.

-g

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=984909
Received on 2008-12-16 11:26:44 CET

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.