See More
Popular Forum

MBA (4887) B.Tech (1769) Engineering (1486) Class 12 (1030) Study Abroad (1004) Computer Science and Engineering (988) Business Management Studies (865) BBA (846) Diploma (746) CAT (651) B.Com (648) B.Sc (643) JEE Mains (618) Mechanical Engineering (574) Exam (525) India (462) Career (452) All Time Q&A (439) Mass Communication (427) BCA (417) Science (384) Computers & IT (Non-Engg) (383) Medicine & Health Sciences (381) Hotel Management (373) Civil Engineering (353) MCA (349) Tuteehub Top Questions (348) Distance (340) Colleges in India (334)
See More

I am going to start with GIT (at work) - should I use GUIs, GUIs/terminal or only terminal?

General Tech Learning Aids/Tools
Max. 2000 characters

Deepak Parmar


( 6 months ago )

I am new got GIT and we are going to start using it at work (migrating from SVN used with Eclipse).

My question is:

In the long run, what is smarter? Learn using GIT via multiple GUI applications, using multiple GUI applications and the command line or just go full and pure command line?

Is it worth spending time to be crazy good with GIT only using the command line commands? Can you do everything with command line? The down side is that its just waste of time - and just plain stupid to go command line 2010.

or is it smarter to mix both command line and GUI applications depending on what I should do? The downside of that is you will be crippled without your GUI applications.

Any comments are appreciated.

Update: Visualize branches is of course done with GUI-applications, but for every day work:

  • Only GUIs?
  • GUIs/command line?
  • Only command line?

Charles Kyobe


( 6 months ago )

Personally, I use the command line and gitk. The only time I really use git gui is when I need to stage only a few files that I've changed, and I've changed a lot of other files, such that using git add -i . really isn't practical.

Anywho, I'd learn the command line first. Once you know your way around the Git commands you won't want a fancy GUI at all. But don't be shy of using gitk --all to visualize the repository, especially if you are a visual learner (like me). Understanding what your commands are doing by seeing their effect on the repository commit graph can be a very powerful learning aid.

what's your interest