[FFmpeg-cvslog] help

[Stephen Gartrell]

helpSteve Gartrell
Netsential.com, Inc
14550 Torrey Chase Blvd., Suite 395 
Houston, Texas 77014 
www.netsential.com 
877-993-6433 x101 toll free 
281-631-9900 x101 direct 
832-265-8511 mobile 
281-631-9597 fax 
-----Original Message-----
From: <ffmpeg-cvslog-request at mplayerhq.hu>
Sent 7/18/2008 5:00:01 AM
To: ffmpeg-cvslog at mplayerhq.hu
Subject: ffmpeg-cvslog Digest, Vol 40, Issue 54Send ffmpeg-cvslog mailing list submissions to
ffmpeg-cvslog at mplayerhq.hu
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-cvslog
or, via email, send a message with subject or body 'help' to
ffmpeg-cvslog-request at mplayerhq.hu
You can reach the person managing the list at
ffmpeg-cvslog-owner at mplayerhq.hu
When replying, please edit your Subject line so it is more specific
than "Re: Contents of ffmpeg-cvslog digest..."
Today's Topics:
1. Re: r14267 - trunk/libavcodec/ra288.c (M?ns Rullg?rd)
----------------------------------------------------------------------
Message: 1
Date: Fri, 18 Jul 2008 09:03:53 +0100
From: M?ns Rullg?rd <mans at mansr.com>
Subject: Re: [FFmpeg-cvslog] r14267 - trunk/libavcodec/ra288.c
To: FFmpeg Subversion commit log and discussion
<ffmpeg-cvslog at mplayerhq.hu>
Message-ID: <yw1xsku7r53q.fsf at thrashbarg.mansr.com>
Content-Type: text/plain; charset=iso-8859-1
Benoit Fouet <benoit.fouet at purplelabs.com> writes:
> M?ns Rullg?rd wrote:
>> Vitor Sessak <vitor1001 at gmail.com> writes:
>>
>>> M?ns Rullg?rd wrote:
>>>
>>>> Vitor Sessak <vitor1001 at gmail.com> writes:
>>>>
>>>>
>>>>> Diego Biurrun wrote:
>>>>>
>>>>>> On Fri, Jul 18, 2008 at 12:42:23AM +0200, vitor wrote:
>>>>>>
>>>>>>> Log:
>>>>>>> Simplify
>>>>>>>
>>>>>> Can we *please* have more descriptive commit messages?  How long can it
>>>>>> take you to explain *what* you simplified?
>>>>>>
>>>>> For such obvious cleanups I'm against spending more time thinking about
>>>>> the commit message than doing the code changes (even more so as what is
>>>>> "cleaner" is a matter of taste, so it is non trivial to explain why the
>>>>> new code is better in a commit msg). But if you could suggest anything
>>>>> better that I could copy-paste for those kind of clean-up commits, I'd
>>>>> happily do so.
>>>>>
>>>> A simple "ra288:" prefix would suffice in this case.
>>>>
>>> Then we go back to the flamewar about if the commit messages should be
>>> understandable with or without seeing the list of changed files. From
>>> what I followed of the discussion, this is a problem almost only for
>>> git.
>>>
>>
>> Here's some sample output from "svn log":
>>
>> ------------------------------------------------------------------------
>> r14274 | mru | 2008-07-18 02:07:17 +0100 (Fri, 18 Jul 2008) | 4 lines
>>
>> MPEGTS: Improve probe function
>>
>> When a sync byte is found, check that transport_error_indicator is zero,
>> and adaptation_field_control is valid (non-zero).
>> ------------------------------------------------------------------------
>> r14273 | bcoudurier | 2008-07-18 01:24:31 +0100 (Fri, 18 Jul 2008) | 1 line
>>
>> cosmetics, remove space
>> ------------------------------------------------------------------------
>> r14272 | bcoudurier | 2008-07-18 01:23:37 +0100 (Fri, 18 Jul 2008) | 1 line
>>
>> return max score when ftyp atom is encoutered
>> ------------------------------------------------------------------------
>> r14268 | vitor | 2008-07-17 23:59:53 +0100 (Thu, 17 Jul 2008) | 1 line
>>
>> Simplify
>> ------------------------------------------------------------------------
>> r14263 | diego | 2008-07-17 17:28:48 +0100 (Thu, 17 Jul 2008) | 3 lines
>>
>> Replace LDLATEFLAGS hackery by proper LDFLAGS tests.
>> The original reasons for LDLATEFLAGS are lost in the mists of time.
>>
>> ------------------------------------------------------------------------
>>
>> Looking at this, how would you know what was simplified in r14268?
>> Contrast this with the information given for r14274.
>
> come on, you just have to add a -v to your command line, and you'll get
> the changed path
> I really don't see the point of all this...
Damn it, you guys really are thick.  THE FILENAME IS NOT EVERYTHING.
Please, PLEASE, go back and read what I've written previously about
this.  I don't want to repeat it all over again.
--
M?ns Rullg?rd
mans at mansr.com
------------------------------
_______________________________________________
ffmpeg-cvslog mailing list
ffmpeg-cvslog at mplayerhq.hu
https://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-cvslog
End of ffmpeg-cvslog Digest, Vol 40, Issue 54
*********************************************