Git Support ready-ness

Nicolai Haehnle nhaehnle at
Mon Sep 6 08:52:22 UTC 2010

Speaking only as a user here...

On Mon, Sep 6, 2010 at 8:30 AM, Andreas Pakulat <apaku at> wrote:
> On 06.09.10 02:37:05, Aleix Pol wrote:
>> On Sun, Sep 5, 2010 at 5:17 PM, David Nolden <zwabel at> wrote:
>> > About the Git menu entries again:
>> > - I find the "Update" menu entry confusing. Seems like it does the
>> > same as "Pull", but there is also a "Pull" entry, so the "Update"
>> > entry should disappear.
>> >
>> I agree, but I'm not sure if we should go deeper, maybe we could consider
>> pull a type of update or something like that.
> Pull is the git equivalent of svn update (roughly). But having both is
> indeed not really good. So one has to go. Ideally I wanted to have
> common actions (among all vcs) named similarly in all menus. So the
> question is why was Pull added at all, when Update was already there...
> And maybe Update is not the best text, how about "Update from
> Repository".

What's wrong with "Pull"?

I realize that other VCS don't necessarily use that term, but Git
does, and Git is already reasonably well known by people. If I as a
git user were to try out KDevelop's git support, I would see the
"Update" option and I would be confused and unsure about what it does.
Sure, I would probably try it out at some point and conclude that what
it really does is "Pull". So why not just call it "Pull"?

There is tons of literature out there already explaining what the
difference in terminology is to people who migrate from SVN to Git. I
don't see why you would want to add to that literature an explanation
of "Deviations from Git terminology in KDevelop".


More information about the KDevelop-devel mailing list