[FFmpeg-devel] ffmpegs future version control system
Sat May 12 23:15:24 CEST 2007
Michael Niedermayer <michaelni at gmx.at> writes:
> On Wed, May 09, 2007 at 04:00:24AM +0200, Luca Barbato wrote:
>> Michael Niedermayer wrote:
>> > * all the web interfaces to git ive seen suck, nothing looks remotely
>> > as sane as viewvc
>> Probably asking for the specific features the git people could lead at
>> least to some directions. I'm using gitweb for tracking the lscube
>> projects and isn't _that_ ugly (yes I had seen something better).
> what i disslike on gitweb most is that its unintuitive, viewvc is alot more
> intuitive ...
> then how do i view a diff for a specific change and file, if i click on
> "history" for the specific file and then on "commitdiff" it shows a
> diff covering many files, if i click on "diff to current" it shows a diff
> against head ...
Click the commit title to get the full commit description. This page
has a list of all files changed along with a 'diff' links that bring
up diffs for each file individually. I suppose including this link in
the file history list would only require a minor change.
> then what about colored diffs, what about colored source code
Diffs are coloured. I agree coloured source code would be nice.
> then blame, just shows the sha1 checksums of the commits but not the
If you point the mouse at a commit ID it pops up the author and date.
> and i suspect it also doesnt follow copies and moves ...
> now who on earth cares about the sha1 checksum?! the silly gitweb should
> show the authors and maybe a short date and if the user then clicks on it
> show the corresponding diff/sha1/...
The sha1 checksum defines the commit. It's the equivalent of revision
numbers in cvs and svn.
> then i dont see any help which would explain what a "blob, commitdiff, tree,
> ... is"
There is ample git documentation elsewhere. I don't expect a web
interface like gitweb or viewvc to include full documentation on the
mans at mansr.com
More information about the ffmpeg-devel