On Tue, Mar 15, 2016 at 02:24:10PM +0100, Przemysław Sobala wrote: > W dniu 01.01.2016 o 15:19, Michael Niedermayer pisze: > (...) > > > >Also ill likely make another round of point releases from the > >2.8/2.7/2.6/2.5 branches soon, that is if someone wants to backport > >something or fix and backport ... > > > > I know it's a bit late but could you backport fixes for #4841, #4849, > #5121, #5267 and also 2241cc17606a616a227613c166ddd3ac789f3798 to 2.8 at > least?
thats not a commit hash, that hash points to a file also for backports the commit hashes are needed not ticket numbers and ideally a git branch that contains them where you tested that the backports work and do what they intend to do A "I want the fixes for tickets so and so backported" isnt really that helpfull i want all fixes backported too ideally would be a "please backport comit abcde12345 to releases/a.b, ive tested it, it applies cleanly, fixes the ticket and passes fate" "ive rebased the commit 234567, to releases/c.d it didnt apply cleanly please merge/cherry pick from my branch at github.com/whatever" [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB In a rich man's house there is no place to spit but his face. -- Diogenes of Sinope
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
