[FFmpeg-trac] #1873(undetermined:reopened): support zygoaudio
FFmpeg
trac at avcodec.org
Wed Jun 5 00:27:13 CEST 2013
#1873: support zygoaudio
-------------------------------------+-------------------------------------
Reporter: ami_stuff | Owner:
Type: enhancement | Status: reopened
Priority: wish | Component:
Version: git-master | undetermined
Keywords: speex zygo | Resolution:
Blocking: | Blocked By:
Analyzed by developer: 1 | Reproduced by developer: 1
-------------------------------------+-------------------------------------
Comment (by cehoyos):
Replying to [comment:18 mikhailov]:
> Replying to [comment:17 cehoyos]:
> > Replying to [comment:16 mikhailov]:
> > > @cehoyos any other commits related to '''libspeex''' have been
merged
> >
> > I was unable to find any libspeex patch that was merged into
origin/release/1.2, could you elaborate?
>
> I've attached all commits relate to '''libspeex''', 2 files: master and
tag 1.2.1 (sorry file names are reversed)
(Please do not attach screen shots on this bug tracker, it is very unusual
that they are helpful, and this is not an exception, link to
http://git.videolan.org/?p=ffmpeg.git instead or post the output of git
log.)
None of the commits shown in your screen shot was merged into
origin/release/1.2, they were all made before origin/release/1.2 was
created.
> > > but this one (dated Jan 16 2013)
> >
> > just for completeness: The patch was committed on March 23rd (after
origin/release/1.2 was branched)
(Sorry for the bad wording: The commit in question was ''pushed'' on March
23rd)
> yes, probably it was wrong rebase or any other history rewrite, commit
date is Sat Mar 23 2013 14:45:58 GMT
Nothing about this change indicates a wrong rebase or a history rewrite,
it was written and committed locally by ami_stuff in January, sent to
ffmpeg-devel and finally pushed on March 23rd.
> > > still in master only, I wonder if any reason or it's been forgotten?
> >
> > Allow me to repeat: Why should it be merged? Is the patch security
relevant or does it fix a regression?
>
> we guess it can help us with ticket #2085
This seems very unlikely to me, but do I understand correctly that ticket
#2085 is fixed in git head and e26b066 but was still reproducible with
785b849 ?
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1873#comment:19>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list