[chirp_devel] git vs hg patches [was: [PATCH 1/4] chirp.py: add --list-radios option (#2343)]
Zach Welch
Tue Feb 24 09:15:01 PST 2015
On 02/24/2015 06:56 AM, Dan Smith wrote:
...
> I have a lot of tooling built around pulling patches from the mailing
> list, testing them, applying them, etc. It's a very smooth process, so
> in the same spirit as the above, please don't make me do something
> totally different and manual just to apply yours.
When designing parsers, the rule is to be strict in what you emit and
liberal in what you accept. I think that's also a good rule when it
comes to handling patches in an open source project. Creating a script
to import a git patch series would be a one-time process, and it lowers
to bar of entry for potential contributors.
But I'll suck it up and learn to push my patches through Mercurial. I'm
still going to use git and hg-git for my development though, because the
workflow is so ingrained.
--
Zach Welch
Mandolin Creek Farm
www.mandolincreekfarm.com
farm: 541-453-4131
cell: 541-740-3410
More information about the chirp_devel
mailing list