search

git-for-windows / git

A fork of Git containing Windows-specific patches.
http://gitforwindows.org/
Other
8.33k stars 2.53k forks source link

Adopt Git Extensions as Git GUI replacement #499

Closed ismyrnow closed 8 years ago

ismyrnow commented 8 years ago

Just wanted to start a conversation about the potential adoption the Git Extensions project as the official Git Gui application. It seems like it's trying to solve the same problems, and has a much nicer GUI. I've been using it for years, and it's very robust and easy to use.

I'm not a maintainer of Git Extensions, but I've supported it financially in the past, and would hate to see that project die off (it has an issue list a mile long) when it seems to be preferable to Git GUI.

l-cornelius-dol commented 8 years ago

I'm an Atlassian SourceTree user myself, and quite like it. However, I just took a look at Git Gui distributed with Git for Windows, and have to say it's truly awful. I don't mean to offend anyone, but it's aesthetically and functionally way behind the SourceTree. Just my two cents. If Git Extensions is an improvement, I say go for it.

linquize commented 8 years ago

You should install GitExtensions directly (SetupComplete.msi), which bundles Git for Windows. Rather than include it here.

VictorVG commented 8 years ago

I liked more TortoiseGit and I take it as a shell. But why not do both in PC-BSD/TrueOS Server - the core of one FreeBSD UNIX, shell and everyone can choose to suit your needs and taste. What sense to impose all their personal habits? I was completely satisfied with for example the possibility of using universaplnoe instrumental core of the package put together for specific tasks without thinking that someone of my choice colleagues may not like.

I do not impose their views just expressed my opinion and if the maintainer of the project will make changes - will develop new methods of work take account of them, well, old sent to landfill. Honestly after SVN I'm still getting used to very carefully Git, but I hope I'm in the minority.

dscho commented 8 years ago

It seems there is enough contention which GUI to use/is better/rocks/sucks that it is safer to keep things as-are than to make everybody angry.

PhilipOakley commented 8 years ago

Personally, I use the 'git gui' (and 'gitk') as my main visualisation tool. I did try GitExtensions for a while but it felt too much like it was trying to be an old style VCS. I still have it installed and occassionally look at it.. but usually fall back to the bash git-cli [command line interface] for whatever tricky problem I have.

It's a "horses for course" sort of thing. I would not want the 'git gui' dropped. If the GitExtensions was included I wouldn't complain.

In the longer term, once (if) the automated packaging eventually becomes a reality, then it shouldn't be any problem to have both a minimal G4W package, and a 'Kitchen sink' package (Though I doubt we'll ever reach that tevel of perfection, given the length of the tool chain and the shifting ground of their communities/corporations)

</$0.02>

dscho commented 8 years ago

If the GitExtensions was included I wouldn't complain.

You would not, others would, and I would be stuck with maintaining yet another piece of software ;-)

shiftkey commented 8 years ago

:thumbsup: to keeping this simple and based on upstream Git wherever possible.

It's rather easy to extend the Git SDK and build your own flavour of distribution, but that's a story for another day...

dscho commented 8 years ago

It's rather easy to extend the Git SDK and build your own flavour of distribution, but that's a story for another day...

@shiftkey true, I should probably write something up. Or maybe we can do that together? But as you say, another day...

shiftkey commented 8 years ago

@dscho you have enough on your plate right now. I'm happy to sketch something out later this week or next week.

kostix commented 8 years ago

I'm ambivalent about adding Git Extensions (or whatever) to GfW, but please don't remove the trusty default tools in favour of anything else. git gui and gitk might look odd to WPF and metro fans but they have two killer features: 1) they're well known; 2) they are supported upstream.

The mere fact Pat Thoyts could be asked to help with problems in those tools makes me confident in their good future :-) (On a side note, I'm rather well versed in Tcl/Tk and might be of help just in case.)

One another note in defence of the standard tools: one should not forget they're cross-platform. For those of us who happens to not only develop on Windows, this is a nice bonus.

linquize commented 8 years ago

Since gitk/git gui is cross platform, the user experience should be consistent. @kostix mentioned a good point: supported upstream by git-core

ismyrnow commented 8 years ago

I didn't know that git gui has upstream support or works cross platform. Very good to know. On Wed, Oct 21, 2015 at 11:06 AM linquize notifications@github.com wrote:

Since gitk/git gui is cross platform, the user experience should be consistent. @kostix https://github.com/kostix mentioned a good point: supported upstream by git-core

— Reply to this email directly or view it on GitHub https://github.com/git-for-windows/git/issues/499#issuecomment-149925891 .