[fpc-devel] Parallel processing in the compiler
graemeg.lists at gmail.com
Sun Sep 5 19:04:31 CEST 2010
On 5 September 2010 18:00, Florian Klämpfl wrote:
>> Juha has a valid point about less conflicts.
> How do you know if you don't use svn? I tried hg and sometimes I use git
I've only used git for the last two years. So no, I don't use svn any
more, but for many years before git, I used svn. So indeed, I can
comment on my experiences with both tools.
> Usually it's even worse than with svn because compared with TortoiseSVN,
> git and hg gui support is still poor, TortoiseHg/Git are far from being
> there. Though git/hg are sometimes usefull to move changes quickly
> between machines.
I'm not a GUI junkie. SVN and GIT started as console tools, and that
is where the power normally lies. As for TortoiseXXX... they are not
the sole provider for "gui" font-ends to git (or other SCM's for that
matter). So don't judge git by simply look at TortoiseGit - it's quite
well known that TortoiseGit is far behind in actual git features. Git
includes it's own gui tools that are a lot more powerful (features
supported), than any others I have seen (and yes, there are plenty
available). Most gui fontends don't even come close to what git can
actually do. The default gui tools included with git use the Tk
widgetset, so it's not the prettiest tools. But when it comes to
getting the job done, I'm not after looks, but rather features and
usability. 'git gui' and gitk accept any parameters like 'git' itself
does (probably unknown to many). So their behaviour and functionality
can change depending on those parameters.
> To be able to get a review of a patch, he needs to publish it in any
> form anyways. So local branches/rebases etc. are pretty useless in this
Rebase is still usable in a published branch (git project itself uses
it like that too), as long as you make it clear to developers that the
history of the branch will change from time to time, and thus its
meant for review/test purposes, and not for developing on. So pushing
a local branch to a published "review" branch is a simple task - many
projects use it and normally reserve a specific branch just for that
Anyway, enough said on the subject.
- Graeme -
fpGUI - a cross-platform Free Pascal GUI toolkit
More information about the fpc-devel