On Fri, Sep 05, 2008 at 01:34:08PM -0500, John Freeman wrote:
> Christopher Faylor wrote:
>> On Sun, Aug 17, 2008 at 03:01:03PM -0500, John Freeman wrote:
>>   
>>> Daniel Berlin wrote:
>>>
>>>     
>>>> It's listed on the wiki that explains how to maintain branches :)
>>>>         
>>> I had no idea such a wiki even existed.  It would really help future 
>>> contributors, I'm sure, if, perhaps during copyright assignment, there 
>>> were some sort of "introduction" process that clearly communicated 
>>> policies.  Thank you for the heads up.
>>>     
>>
>> But, you did do it again, just a little while ago.
>>   
>No, I didn't.  I have made one commit in the past week, with a
>one-liner log message.  This morning I used Mr.  Lopez-Ibanez's advice
>in his earlier post, number 148771,

I don't know what post number 148771 is (it's 2008, we can use URLs
these days) but

>entitled "broken svn commit logs and how to fix them" and changed the
>log message for revision 139145.  I haven't done a merge since the last
>time this issue came up.

I'm not making this up:

    Subject: Bug 31754
    Date: Fri, 05 Sep 2008 14:39:56 -0000
    To: gcc-bugzilla
    From: jfreeman

    Author: jfreeman
    Revision: 139145
    Modified property: svn:log

    Modified: svn:log at Fri Sep  5 14:39:56 2008
    ---------------------------------------------------------------------------=
    ---
    --- svn:log (original)
    +++ svn:log Fri Sep  5 14:39:56 2008
    @@ -1,19740 +1,1 @@
    -Merged revisions 136194,136196,136200,136209,136215-136217,136221-136222,1=
    36229,136235-136239,136242,136247,136249,136251-136254,136266,136273,136276=
    -136277,136280,136282-136283,136291-136297,136301-136304,136308,136311,1363=
    14-136315,136319-136323,136329,136331,136344,136348,136351,136355,136359-13=
    6360,136362,136372,136374,136376-136378,136383,136386,136389,136395,136406,=
    136416,136421,136423,136425,136427-136428,136431,136433-136435,136437-13643=
    8,136485-136486,136491,136494,136497-136498,136503,136506,136513,136517-136=
    518,136532,136534,136536-136537,136539-136542,136544-136547,136551,136554-1=
    36555,136561-136563,136566-136569,136574,136576,136578,136580,136583,136585=
    ,136590,136596,136600-136602,136604-136605,136609,136615,136617,136619,1366=
    32,136636,136639,136641,136645,136647-136651,136653-136655,136657-136658,13=
    etc.

This exhibited the same bounce behavior that we saw last time.

Reply via email to