The State of Go

Re:The State of Go by kasey_junk on Saturday February 14, 2015 @06:58PM (#9051211)

The simplest reason is if what I was contributing was done on my employers time and they have strict IP restrictions. It is much, much easier to vet a single changeset than it is to a) verify a whole repo history and b) coordinate around my public/private github identities.

[ Parent | on HN ]

Re:The State of Go by lomnakkus on Saturday February 14, 2015 @10:03PM (#9051634)

I'm not sure I understand. Vetting a changeset is basically the same thing as verifying the repo. Just look at the hash of repo A (your clone), check that it matches B (upstream), check that your repo A + "patch" matches pull request.

What am I missing?

[ Parent | on HN ]

Re:The State of Go by kasey_junk on Sunday February 15, 2015 @07:29AM (#9052431)

Branches and the ref log.

[ Parent | on HN ]

Re:The State of Go by Mithaldu on Saturday February 14, 2015 @07:06PM (#9051242)

I was hoping for more reasons, since the very first and simple one is usually the one that has the most and simplest workarounds. You could for example make a patch with git on your local machine and attach that to an issue.

[ Parent | on HN ]

Re:The State of Go by kasey_junk on Saturday February 14, 2015 @07:15PM (#9051267)

And then I have to follow a completely different work flow and inconvenience the maintainers.

[ Parent | on HN ]