3 ms·

To be honest, i feel like git really needs better wrappers or a better GUI or better defaults. There shouldn't be a quadrillion command flags to know for simple

by buster 12y ago

To be honest, i feel like git really needs better wrappers or a better GUI or better defaults. There shouldn't be a quadrillion command flags to know for simple tasks like this. And i don't mean the -S but the "use -S instead of -s but for other things use -asm, oh and then you have command xyz which takes --<long option> followed by other options, but only use those if your SHA hash can be divided by 3.141 and it's full moon".

mschuster91 12y ago
For Windows there exists TortoiseGIT, sorta fork of TortoiseSVN. Not sure if anything similar exists on Linux or if it could even be done the easy way ("right-click in explorer"), due to the multitude of file explorers/desktop environments.
- buster 12y ago
  Linux GUIs are rather poor and usually you just use the CLI. It's only that i miss sane defaults and a common sense of workflow amongst the community. Currently it's this huge toolbox that can do everything in thousand ways, but to be honest, i don't want to be able to "get my copy of the sourcecode to the server" in a gazillion ways, i would very much prefer one way and one simple command. If you start googling for "how do i do X in git" you will find 10 ways to do X and 100 philosphical discussions why you should do X in a specific way and about "what would Jes^H^H^H Linus do?". For example, i'd love to have "git init" ask your name, email, if you'd like to sign with GPG, etc. etc. and then save this in git, so that every git commit will be signed with GPG without giving that stupid option. The common way a la "Git" would be to introduce bash aliases, i think. But that doesn't work across machines, OSs or even on the same machine in a different shell.
  - pyre 12y ago
    You can add aliases to ~/.gitconfig (the file created by 'git config --global'). See mine: [alias] lg = log --graph --decorate llg = log --oneline --graph --decorate ll = log --oneline dc = diff --cached st = status --short ci = commit rb = rebase br = branch co = checkout Then you can just run (e.g.): $ git llg
JelteF 12y ago
Try using tig, it will make looking at a repositories history so much easier for you. It's like git log and diff merged together in a command line utility of awesomeness.
deleted 12y ago
[deleted]
Wicher 12y ago
Git is the subject of, in my opinion, some quality satire in this respect: http://git-man-page-generator.lokaltog.net/ http://git-man-page-generator.lokaltog.net/

by buster 12y ago

mschuster91 12y ago

For Windows there exists TortoiseGIT, sorta fork of TortoiseSVN. Not sure if anything similar exists on Linux or if it could even be done the easy way ("right-click in explorer"), due to the multitude of file explorers/desktop environments.

buster 12y ago
Linux GUIs are rather poor and usually you just use the CLI. It's only that i miss sane defaults and a common sense of workflow amongst the community. Currently it's this huge toolbox that can do everything in thousand ways, but to be honest, i don't want to be able to "get my copy of the sourcecode to the server" in a gazillion ways, i would very much prefer one way and one simple command. If you start googling for "how do i do X in git" you will find 10 ways to do X and 100 philosphical discussions why you should do X in a specific way and about "what would Jes^H^H^H Linus do?". For example, i'd love to have "git init" ask your name, email, if you'd like to sign with GPG, etc. etc. and then save this in git, so that every git commit will be signed with GPG without giving that stupid option. The common way a la "Git" would be to introduce bash aliases, i think. But that doesn't work across machines, OSs or even on the same machine in a different shell.
- pyre 12y ago
  You can add aliases to ~/.gitconfig (the file created by 'git config --global'). See mine: [alias] lg = log --graph --decorate llg = log --oneline --graph --decorate ll = log --oneline dc = diff --cached st = status --short ci = commit rb = rebase br = branch co = checkout Then you can just run (e.g.): $ git llg

JelteF 12y ago

Try using tig, it will make looking at a repositories history so much easier for you. It's like git log and diff merged together in a command line utility of awesomeness.

deleted 12y ago

[deleted]

Wicher 12y ago

Git is the subject of, in my opinion, some quality satire in this respect: http://git-man-page-generator.lokaltog.net/ http://git-man-page-generator.lokaltog.net/