Re: Git drawbacks?

[Dmitry Smirnov <divis1969@gmail.com>]

Dmitry Potapov <dpotapov <at> gmail.com> writes:

> And then if you really want
> to have good and clean history, you need more than just a branch. You
> should be able to amend your previous commits while you work on some
> feature. With Git, it is trivial, you just run 'git rebase -i' and may
> edit some previous commits, correct comments, squash fix-ups, etc...
> How can you model that? By creating another branch and moving patches
> to it by hands... Well, it is not very productive time spending, and
> the cost of branch becomes even more prominent.

This is a cool feature, but it contradicts to my understanding of VCS. 
It is some kind of re-writing the history of WWII :-) 
BTW, as I undestood it, it is just a feature that can be implemented 
in any VCS (if you have access to its internals).

> A quick look at "What's cooking in git.git" that Junio posted a few days
> ago reveals that there are at least 43 branches that are cooking now and
> the total number of branches that have been merged to 'master' over all
> Git history is 3290. And Git is not the largest project out there...

I meant 4-5 per person (me, precisely speaking)