macports-changes-bounces

[Bradley Giesbrecht]

Communication with the macports svn server is very slow/stalling for me.

Is anyone else having any macports svn issues?


On Aug 29, 2011, at 3:00 PM, Ryan Schmidt wrote:

> 
> On Aug 29, 2011, at 16:13, Bradley Giesbrecht wrote:
> 
>> I performed an "svn propedit" and received these two emails?
>> 
>> On Aug 29, 2011, at 1:55 PM, pixilla at macports.org wrote:
>> 
>>> From pixilla at macports.org Mon Aug 29 13: 55:02 2011
>>> Date: Mon, 29 Aug 2011 13:55:02 -0700
>>> To: macports-changes at lists.macosforge.org
>>> From: pixilla at macports.org
>>> Subject: propchange - r83328 svn:log
>>> Reply-to: macports-dev at lists.macosforge.org, pixilla at macports.org
>>> 
>>> Author: pixilla at macports.org (original author: pixilla at macports.org)
>>> Revision: 83328
>>> Property Name: svn:log
>>> 
>>> @@ -1,3 +1,3 @@
>>> www/raptor2:
>>> -- Change to raptor temporary depends_lib to depends_build type.
>>> +- Change raptor temporary depends_lib to depends_build type.
>>> - Revbump.
>>> 
>>> _______________________________________________
>>> macports-changes mailing list
>>> macports-changes at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-changes
>> 
>> 
>> On Aug 29, 2011, at 1:55 PM, macports-changes-bounces at lists.macosforge.org wrote:
>> 
>>> Your mail to 'macports-changes' with the subject
>>> 
>>>  (no subject)
>>> 
>>> Is being held until the list moderator can review it for approval.
>>> 
>>> The reason it is being held:
>>> 
>>>  Message has implicit destination
>>> 
>>> Either the message will get posted to the list, or you will receive
>>> notification of the moderator's decision.  If you would like to cancel
>>> this posting, please visit the following URL:
>>> 
>>>  http://lists.macosforge.org/mailman/confirm.cgi/macports-changes/d35fd20c3a8fb49ecdc7597afacccfad26128a48
> 
> I approved the message. I was confused too about why it was being held for moderation; it should have gone straight through. I think there was something corrupted about the headers; I noticed hen the message appeared on the list, the headers appeared in the body of the message. Hopefully it was just a fluke and won't happen again.
> 
> 
> 
> 
>