[FFmpeg-devel] [GIT] ready by the weekend

Andres Mejia mcitadel
Thu Nov 18 03:05:26 CET 2010

On Wednesday 17 November 2010 20:00:18 Luca Barbato wrote:
> On 11/17/2010 08:03 PM, Reimar D?ffinger wrote:
> > On Wed, Nov 17, 2010 at 07:30:19PM +0100, Luca Barbato wrote:
> >> On 11/17/2010 06:47 PM, Reimar D?ffinger wrote:
> >>> On Wed, Nov 17, 2010 at 05:01:31PM +0100, Luca Barbato wrote:
> >>>> j-b and janne should have all the issues sorted during this weekend
> >>>> (hw problems, latest repo checks)
> >>>> 
> >>>> I'll host a mirror of it and keep in sync a copy for github and
> >>>> gitorious (somebody wants a repo.or.cz as well?).
> >>>> 
> >>>> So I guess by the next week we can switch anytime.
> >>>> 
> >>>> Is everybody ready? =)
> >>> 
> >>> No. We don't have a "cheat sheet" for anyone only familiar
> >>> with SVN,
> >> 
> >> I thought there cheat sheets links got already provided many times.
> >> Rafael sent them again anyway.
> > 
> > You can send them 50 times and I still don't care.
> > I can use search myself, the point is that not everyone has to use
> > search themselves, find some document, figure it isn't quite ideal
> > if you're already used to FFmpeg and then some things are explained
> > in a way we do _not_ want them to be done.
> To sum up your request, you'd like a new policy document with the best
> practices for ffmpeg.
> I guess the git-proficient people could start a page on the wiki now.
> The problem I see (from this email) is that some concepts that I
> consider basic aren't exactly clear nor understood.
> Before I star could we come up with a list of doubts?
> > What? Are you suggesting we no longer document who wrote a patch?
> > I really have not the slightest clue what you mean by this.
> please read man git-format-patch and related documentation on the fields
> in a git commit, I considered that as given but apparently isn't =|
> > Because every single time my very specific request was completely
> > ignored, people send links to random documents that have nothing to do
> > with FFmpeg specifically and when I say why it's nonsense everyone
> > suddenly disappears.
> Maybe you could try to start the wiki page with your doubts and I, or
> other people, will try to fill the answers with the best explanations we
> could.
> lu

It would be nice to know what policies/best practices exist that are ffmpeg 
specific. For example, it would be helpful if there was a clear policy as to 
how patches should now be submitted.

Is using git-format-patch mandatory? If so, are there any options that should 
be used? Should conflicts be resolved?

What about those submitting large changes (GSOC project perhaps)? Should they 
instead be encouraged to provide a remote branch hosted somewhere?

Andres Mejia

More information about the ffmpeg-devel mailing list