[Kdenlive-devel] move to git ?

[Dan Dennedy]

On Tue, Mar 3, 2009 at 11:34 PM, Clifford Wolf <clifford at clifford.at> wrote:
> Hi,
>
> On Sat, Feb 28, 2009 at 02:18:08PM +0100, Marco Gittler wrote:
>> since sourceforge now provides SCM also in git, i would ask if someone
>> has anything against moving from svn to git.
>
> usually I'm just a stalker on this list, but since scm is one of my core
> expertises and it looks like there are some strong oppinions on it I
> decided to post my thoughts to this topic..

Thank you for your very helpful and pragmatic comments on this topic.

> first of all: there is almost no good documentation out there for git. most
> so called git tutorioals don't explain anything about how git actually
> works but instead just give the useres some commands to copy and paste.
> this is dangerous imo because git is a so powerfull tool and powerwull
> tools sometimes can be dangerous when users don't know what there are
> doing.
>
> a git introduction that I can actually recommend is "Git from the bottom
> up" by John Wiegley:
>
> http://www.newartisans.com/blog_assets/git.from.bottom.up.pdf

This does seem like a good resource because a brief scan shows me that
at least some terminology is covered at the beginning. Sometimes, I
would get stuck on the terminology used in the git man pages.

> btw: I'm using git a lot for projects that actually are in svn or another
> scm. in this cases I have a local git repository syncing from the projects
> central scm. there I can play around with different branches use rebase and
> all the funny git features and finally send patches to the projects mailing
> lists..

This is also a good point. In fact, perhaps we should let the process
occur naturally and be open to contributors saying "pull this change
from my git tree at ___." After just a couple of those, it would
certainly make sense for a main developer to use git-svn and push it
to a new SourceForge project git repo.

-- 
+-DRD-+