21–30 of 132 posts
Next up for anyone willing to take the bite: Build a unified for CLI for Mercurial and Git. It's a challenge but it's worth it :)
[1]: https://www.mercurial-scm.org/repo/hg/log?rev=keyword%28%27g... [2]: https://www.mercurial-scm.org/wiki/GitExtension
Git is an awesome tool – so awesome that it has a vast plethora of options and commands to do just about anything. Bit attempts to alleviate some of that pain.
Having used most SCM since RCS days, I get to differ, but since I am left without another option, so just like with C and JavaScript, I suck it up and get the job done by whatever means.
- rant mode off
Thanks for bringing a bit more of security into the IT world with a Go version though.
I love the initiative, however the autocomplete popup doesn't work so well. i made a typo and i can't backspace to delete it.
Please file an issue . This is OS/Terminal/Shell specific
The autocomplete/help popups didn't happen for me, is there something I need to do? I'm using zsh on a Mac, perhaps it assumes bash. Aside from that, I'm going to persist with this for a little while and see how it goes, the git interface does bother me.
Next up for anyone willing to take the bite: Build a unified for CLI for Mercurial and Git. It's a challenge but it's worth it :)
There is one (though incomplete)! And it's called Mercurial. Since 5.4 released earlier this year, Mercurial is slowly gaining [1] the ability to operate on local Git repositories with its bundled git extension [2]. [1]: https://www.mercurial-scm.org/repo/hg/log?rev=keyword%28%27g... [2]: https://www.mercurial-scm.org/wiki/GitExtension
Git is an awesome tool – so awesome that it has a vast plethora of options and commands to do just about anything. Bit attempts to alleviate some of that pain.
And all of those commands have an incompatible syntax. SVN is much better in these regards.
The most popular git questions on stackoverflow tells a story on which tasks are more complex on git because you have to know all the internal tricks.
Earlier quoted context omitted.
And all of those commands have an incompatible syntax. SVN is much better in these regards.
Yes! A git cli with a good syntax which is the same for every command would be useful. It would not have to do every nifty git feature, just uses a senseful subset: git push/bull branching/merging/rebasing and add some nifty common problems like delete file from history, remove last x commits already pushed etc. The most popular git questions on stackoverflow tells a story on which tasks are more complex on git becau…
Honest question: what's up with the (2 hours ago) notation? I've seen this before in a couple of git-related and other applications but personally never understood why one would pick this over date/hour. Is this a cultural thing? Do some people actually find this better (from the point of conveying timestamp information)? My main problem with it, apart from not having a high resolution, is that it usually just leads…
This thing has the advantage that you don't need to know the current time and subtract the timestamp from it to see it is 2h old.
For a lot of other stuff it doesn't make any sense at all. E.g. when you have a lot of things all with "2 hours ago" the precision is too low, when you are more interested in the time of day something was happening etc.
Earlier quoted context omitted.
And all of those commands have an incompatible syntax. SVN is much better in these regards.
Yes! A git cli with a good syntax which is the same for every command would be useful. It would not have to do every nifty git feature, just uses a senseful subset: git push/bull branching/merging/rebasing and add some nifty common problems like delete file from history, remove last x commits already pushed etc. The most popular git questions on stackoverflow tells a story on which tasks are more complex on git becau…