[FFmpeg-devel] Who is against GIT now?

Olivier Galibert galibert
Mon Apr 6 11:40:26 CEST 2009

On Sun, Apr 05, 2009 at 11:11:16PM -0700, Mike Melanson wrote:
> Reinhard Tartler wrote:
> >Mike Melanson <mike at multimedia.cx> writes:
> >
> >>>If we switch to git, we can insert the old revision number in the
> >>>commit message.  Searching commit messages is trivial with git.
> >>How will FATE work if, hypothetically, we move to git?
> >
> >E.g. by downloading tarballs from gitweb?
> Here's what I know about git-- that versions look something like:
> 6e6fc12c61446bfe8dff7ce3b50ebfe0b0835bc8
> 8e1f4d881f813d7d2c67656868f39b46a98d320d
> 18c7f1016987ed9d220595e523318fcfb08410ef
> (actual hashes from my FATE code repository). So what should the main 
> page of FATE report regarding the state of FFmpeg code? That version 
> 6e6fc12c61446bfe8dff7ce3b50ebfe0b0835bc8 passed all tests but that 
> 8e1f4d881f813d7d2c67656868f39b46a98d320d had problems?

That's an option.  Seriously.  It may look unweidly (and, well, it
is), but at least when someone has the object 6e6f he knows he has the
correct version.  But I think a better option is to tag tested
versions (I suspect date tags would be efficient) and refer to them.
Especially since you can associate a message to a tag (in addition to
its name), where you could put the test results.  You can gpg-sign
them too if you think you may have integrity issues, but I kinda doubt
it's worth it.


More information about the ffmpeg-devel mailing list