3 ms·
First some context - I'm by no means a Git power-user. I learnt it under duress and would have much preferred Mercurial but at that point it was obvious which w
by andybak 13y ago
First some context - I'm by no means a Git power-user. I learnt it under duress and would have much preferred Mercurial but at that point it was obvious which way the wind was blowing.
Back in SVN days I also used to be quite fond of Google Code as it is was much cleaner and simpler than Github to my eyes (bearing in mind that a lot of Git terminology was unfamiliar to me back then).
But once I learnt enough Git to get by, I started to love Github.
My standard workflow when I need to use a 3rd party app for a project is:
1. Find the original repo on Github,
2. Browse the network to see if any of the forks are more actively maintained or have enough additions to be worth considering pulling from.
3. Fork the best fork to my own account.
4. Make the changes I need and issue pull requests if I think upstream would be interested.
I've never learnt how to use patch sets. If someone sends me a pull request, it's 2 clicks to merge it. I'm sure patch sets aren't terribly hard but I can't see how they'd be easier than that.
- levosmetalo 13y ago> I've never learnt how to use patch sets. If someone sends me a pull request, it's 2 clicks to merge it. I'm sure patch sets aren't terribly hard but I can't see how they'd be easier than that. It's a few clicks if all you want is just to _blindly_ accept and merge it, without having it on your own computer before merging and being able to compile it, run a test suite, or perform some non trivial modifications to patch. For this purpose, to me is much easier to just apply the patch set in my local tree, or add a new remote and checkout branch then to deal with github pull request.
- andybak 13y agoWhat is this 'compile' of which you speak? (and slightly more sadly) What is this 'test suite' of which you speak? :-(