SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Which git-package you would recommend for "real work"?
That is: not just getting SW to install, but to do co-operative SW development.
It wouldn't do exactly harm if it could handle some other kinds of repos too (hg, SVN, ...).
git is a general tool, egit and smartgit/hg look specialized. I would rather say you need to check if those tools suit your needs. (for example egit can help you only if you use eclipse). I suggest you to be familiar with git itself not only just with some GUI frontends. Also you can try gitk. Probably you need to check gerrit too.
git is a general tool, egit and smartgit/hg look specialized. I would rather say you need to check if those tools suit your needs. (for example egit can help you only if you use eclipse). I suggest you to be familiar with git itself not only just with some GUI frontends. Also you can try gitk. Probably you need to check gerrit too.
I have mostly used git and git-gui (or git gui these days).
My experience with hg on the other hand is pretty limited.
I just have the itch that I might come across hg and SVN in the future (used "torture svn" however).
I'm interested in Egit, because I use eclipse often - just never tried Egit.
cp /usr/doc/git-1.8.4/contrib/completion/git-completion.bash /etc/bash_completion.d/.
Add to /etc/bashrc or ~/.bashrc
source /etc/bash_completion.d/git-completion.bash
Scripts also available for ksh, zsh and tcsh in /usr/doc/git...
cp /usr/doc/git-1.8.4/contrib/completion/git-completion.bash /etc/bash_completion.d/.
Add to /etc/bashrc or ~/.bashrc
source /etc/bash_completion.d/git-completion.bash
Scripts also available for ksh, zsh and tcsh in /usr/doc/git...
git is a general tool, egit and smartgit/hg look specialized. I would rather say you need to check if those tools suit your needs. (for example egit can help you only if you use eclipse). I suggest you to be familiar with git itself not only just with some GUI frontends. Also you can try gitk. Probably you need to check gerrit too.
I agree, with all those seemingly helpful tools I've always run into issues eventually and gone back to the command line. Btw, you can say "git gui" on the command line and get a graphical tool (try Repository -> Visualize HEAD's history).
I agree, with all those seemingly helpful tools I've always run into issues eventually and gone back to the command line. Btw, you can say "git gui" on the command line and get a graphical tool (try Repository -> Visualize HEAD's history).
I agree, with all those seemingly helpful tools I've always run into issues eventually and gone back to the command line. Btw, you can say "git gui" on the command line and get a graphical tool (try Repository -> Visualize HEAD's history).
It's really too bad that (AFAICT) absolutely NONE of the people that wrote (I will not say "designed") the git command line interface had the faintest idea on how to write a user interface. It looks like they fed a bunch of perl users a load of crack and told them to go at it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.