An extension for hg using git-flow branch model
yinweiming at gmail.com
yinweiming at gmail.com
Wed Jan 19 03:14:50 CST 2011
Hi Adrian
On Wed, Jan 19, 2011 at 3:51 PM, Adrian Buehlmann <adrian at cadifra.com>wrote:
> On 2011-01-19 03:05, yinweiming at gmail.com wrote:
> > Hi, guys,
> >
> > I am a new comer in this mail group. Say hello to everybody.
>
> Welcome!
>
Thank you.
>
> > I think much people heard about git-flow,
> > http://nvie.com/posts/a-successful-git-branching-model/ .
> > I just write hg flow and using in my own team. I put it on bitbucket.org
> > <http://bitbucket.org>, you can get it here
> > https://bitbucket.org/yinwm/hgflow .
> >
> > If you think that's not bad, please give me some feedback.
> >
> > Thanks so much.
>
> (tl;dr summary: License your extensions under GPL v2+!)
>
> Sorry for the bad news: but your license [1] is most likely ineffective
> for anyone actually trying to use your extension.
>
Sorry for the mistake, I change it into GPL v2.
>
> As soon as your program does things like:
>
> from mercurial import commands
> from mercurial import hg
>
> you are most likely calling into mercurial's internal API [2]. Quote
> (reference added).
>
> Using this API is a strong indication that you're creating a
> "derived work" subject to the GPL. Before going any further,
> read the License page [3]
>
> See also WritingExtensions [4].
>
I will change my code soon for remove all internal API related code.
Thank you.
>
> [1] https://bitbucket.org/yinwm/hgflow/src/tip/LICENSE
> [2] http://mercurial.selenic.com/wiki/MercurialApi
> [3] http://mercurial.selenic.com/wiki/License
> [4] http://mercurial.selenic.com/wiki/WritingExtensions
>
--
yinwm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial/attachments/20110119/5ad1ba10/attachment.htm>
More information about the Mercurial
mailing list