3 ms·
You can easily make an alias for all of those commands. I would say that "git add" is simpler than "git stage add". "git stage remove" would definitely be nice
by zaius 17y ago
You can easily make an alias for all of those commands.
I would say that "git add" is simpler than "git stage add".
"git stage remove" would definitely be nice. "git reset HEAD file" is a bit clunky.
What would "git stage list" do?
Saving empty directories is annoying. Just touch an empty ".gitignore" file in the directory and you can then add the directory.
If you don't like making your history cute, and you don't see any advantages, don't do it!
- d0m 17y agoI won't fix git bad command line interface. You'll agree with me that it's plain stupid to start creating aliases for such basic commands. However, I'll be happy to create alises for more complicated stuff. I mean, I shouldn't have to use alias to fix git' bad command line interface. git stage list would be a kind of git status. To stage file, I use git add. To view them, I use git status. To remove a file from a stage, I use git reset .. That's just plain wrong and annoying. It's like that for every part of git. I don't see why saving empty directories is annoying. If I don't want a directory, I'll just remove it? Or in the opposite, if I want an empty directory, I'll add a directory? Why should I put a hidden file inside a directory to have it added by git? Finally, for the history, I'm just saying that's it's too complicated for nothing. Of course I can avoided it. I also can use SVN and avoid branch because they are complicated, but that's not the point.
- zaius 17y agoI was agreeing that saving empty directories is difficult - it's annoying that you have to put an empty file in them.