Whoops, somehow the mailing list wasn't on CC. Here is our conversation:
On Wed, Sep 24, 2014 at 8:35 AM, Lode Leroy wrote:
> thanks for your quick (!) response.
> is there no other way than github pull-ing? I hate to have to maintain
> a clone of your repository just to submit a few trivial patches...
Understood. The other way is to have someone else submit it (like in the
old days before GitHub) but tends to be a slippery slope. I did this with
some help content ("what is this?" text in the software) and I was being
asked to fix stuff I did not create, so I try to avoid submitting patches
on behalf of others.
GitHub lets you easily delete said branch/fork/project clone too (after the
pull is accepted please) which cleans up your project listing. It also
allows you to commit changes to the pull while it is under review, which is
tremendously useful for the ones accepting the change. Overkill for your
cmake fix? Probably. But I find it top notch and far superior over the
old diff/tarball methods. It truly makes GitHub a place for bug discussion
and allows the mailing list to be a place for higher-level feature
conversation or general devel help. :).
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
LMMS-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmms-devel
