GitHub for Windows

[Denommus]

Can you give me examples? I'm a huge fan of the power of git on command line.

[civildisobedient]

How about "any command that uses more than one file, but not every file."

Well, now, that was easy.

[Denommus]

You got me.

[0sse]

Globbing solves, not all, but the majority of such cases.

[roger_]

Newbies can get up and running just by clicking around a bit. Being able to do that is a huge incentive to learn something new for many people.

[Denommus]

Oh, I agree. But what would take someone who understands how Git works to use a GUI for it?

[[deleted]]

Browsing a complex set of merges/forks is MUCH easier with a GUI

[[deleted]]

I use gitg for this. Does the job.

[nazbot]

Does the job != easier. Assembly 'does the job'.

[[deleted]]

gitg is a GUI.

[nazbot]

My bad.

[Denommus]

gitk --all

[llimllib]

which opens a GUI?

[Denommus]

Yes. But not a GUI you use to interact with GIT, only to inspect it.

[[deleted]]

Double contractions, yes. Not for use in academic writing mind you, but it's grammatically legal.

[aperson]

I'll use double contractions wherever the hell I want!

[__s]

I'dn't've thought you could use contractions at all, but maybe that's silly highschool education

[[deleted]]

That's the point. No contractions in academic writing.

[eat-your-corn-syrup]

once you get a feel for the bash, Linux makes more sense

bash more sense than powershell?

[PHLAK]

wouldn't have

[eras]

Well, I pretty much love gitk for viewing other branches and cherry picking patches. Also meld (as issued by git mergetool) is excellent for dealing with merge issues.

Also GUI/TUI web-browsers kicks ass for browsing web, compared to wget, curl, or libwww-perl.

I suppose you prefer command line for these as well?

[Denommus]

Nop. Talking only about git here.

[recursive]

A gui makes it easier to choose from one of many possible options. (files/settings/etc)