[FFmpeg-devel] [RFC] Some git questions

Stefano Sabatini stefano.sabatini-lala
Sat Feb 5 13:24:43 CET 2011


starting this thread because I think other may benefit for the
eventual answers.

I'm considering to create a separate public git repo for libavfilter
work in progress.


* people can easily download the repo and use the stuff if interested,
  eventually contribute to it

* it would be easier to understand the logic of each single patch for
  the reviewer, as she can "look forward" in the patch series

* "main" repo stability is not compromised.
  For example in the case of audio filtering, I could work on it until
  a complete regression test is ready, after that integration
  in the main repo would be safer.


I tend to do a lot of rebasing to my local branches, for getting
each patch "series" in shape before committing to the main repo.
Supposing that both users and contributors pull from the repo, how
would that affect their workflow?
I.e. which is the consequence for the other users/committers if a
committer rebases one branch and pushes it? Or should rebasing to
remote repos just be disabled?

The alternative I can see is directly merging a "dirty" branch, *or*
creating dedicated rebased branches for integration, which shouldn't
be too much work as it may be done just once when a branch is
considered ready for integration.
FFmpeg = Formidable & Faithless Magic Picky Evanescent Gadget

More information about the ffmpeg-devel mailing list