I have to agree with Barry for 2 reasons: New users ease of understanding in a visual screen with helps AND the comfort of visually seeing the intent of what you are doing.
CLI has never given this, visually. (And I do recognize the ability of "all" uses of CLI, overall.) I do admit, EVERYTHING has shortcomings; whether screened uses or CLI.
This type of approach, Barry is showing, is very useful delivering a useful level of clarity.
+1
Github and SmartGit
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
The return of SmartGit!
http://barryk.org/news/?viewDetailed=00576
I wanted to make my work with OpenEmbedded available to everyone, and decided that github is the way to go.
Due to prior reasonably positive experiences with SmartGit, I have installed it on my PC. So far, working well.
I create a new 'oe-qky-src' repo on github, then in SmartGit cloned it, then copied in my local files, committed and pushed them. That all went well, intuitively.
http://barryk.org/news/?viewDetailed=00576
I wanted to make my work with OpenEmbedded available to everyone, and decided that github is the way to go.
Due to prior reasonably positive experiences with SmartGit, I have installed it on my PC. So far, working well.
I create a new 'oe-qky-src' repo on github, then in SmartGit cloned it, then copied in my local files, committed and pushed them. That all went well, intuitively.
[url]https://bkhome.org/news/[/url]
Couple of primers on Git
https://product.hubspot.com/blog/git-an ... -beginners
https://guides.github.com/activities/hello-world/
https://product.hubspot.com/blog/git-an ... -beginners
https://guides.github.com/activities/hello-world/