On Monday, July 23, 2012, Diego Biurrun <[email protected]> wrote: > Ahem, it seems to be the brown paperbag season again... > > So, I slipped up and accidentally pushed some ongoing work I had on > my master branch to origin/master, namely the following commits: > > 0abed1d13fdc0fb04873a7763e7a765ba621d66a > aacps: Drop some function argument const qualifiers to silence gcc warnings > > f78701167944369f4ed9828545a8e25449c00c9f > build: cosmetics: Align all backslashes on column 72 > > 0065a92b7ce45d6074d64102a898bcee6c839400 > Initialize some variables to shut up compiler warnings > > 8ddb529831fc13d803589b88e9b47da68674b599 > dv: Split off DV video encoder into its own file > > 3a908aea69cf9a4ce8c221fd8b17bbfaad34c033 > Drop support for completely obsolete Gopher protocol > > I created a fresh branch with only the two commits I wanted to push, > but git-push took me by surprise by sending my master branch and not > the push branch I had created. I'm not entirely sure if I should have > expected that or not. > > I took the Git server offline in roundabout a minute, so hopefully > nothing should have picked up the stray commits. The repo is fixed > now and HEAD is pointing to the commit that it should point to. > Mail notifications for the above set arrived on libav-commits, but > you can ignore it, the commits are no longer on origin/master. > > Sorry for the mishap. I'll see if I can whip up some documentation > updates on how to avoid such mistakes tomorrow. > > Diego - wearing his fool's hat
Hi Michael, It looks like the PA-RISC FATE runs require manual intervention after Diego's little boo-boo. -- Sean McG.
_______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
