[FFmpeg-devel] [PATCH v2] add put_bits_long to avoid undefined behaviour in put_bits
Michael Niedermayer
michaelni
Wed Aug 26 12:48:48 CEST 2009
On Tue, Aug 25, 2009 at 09:45:08PM +0200, matthieu castet wrote:
> Hi,
>
>>> + else{
>>
>> should have {} for simplicity of future patches
>>
>>> +}
>>> +
>>> /**
>>> * Returns the pointer to the byte where the bitstream writer will put
>>> * the next bit.
>>
>> tabs are forbidden in svn
>
> Done in the attached patch.
no the tabs are still there
>
>
> Matthieu
>
> PS : sorry for creating a new thread, but I don't received mail from ML,
> and reply to me seems dropped.
IIRC mailman kills reply-to, we configured it that way because mailman
sucks
our choices are
1. leave reply-to as it was and accept that many replies will not reach the
list
2. force reply to the list
the option id love to have is making sure that ffmpeg-dev is always one
of the addresses of reply-to but the existing ones are left, but mailman
does not support this, at least not last time (years ago ...) when i
checked ...
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
When you are offended at any man's fault, turn to yourself and study your
own failings. Then you will forget your anger. -- Epictetus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20090826/37c287bb/attachment.pgp>
More information about the ffmpeg-devel
mailing list