From: Richard Jones <rich@annexia.org>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] ocaml as editor extension language
Date: Tue, 5 Jan 2010 11:08:37 +0000 [thread overview]
Message-ID: <20100105110837.GC9256@annexia.org> (raw)
In-Reply-To: <201001051004.24322.jon@ffconsultancy.com>
On Tue, Jan 05, 2010 at 10:04:24AM +0000, Jon Harrop wrote:
> 1. You do not have the right to distribute your source code freely and must
> distribute only independently (e.g. patches only).
Tools like quilt and git-rebase are now so good at handling "base +
patches" that I wouldn't say this is much of an issue these days.
At Red Hat we routinely deal with kernel + 100s of patches on top,
many of which conflict, and freely inserting and removing patches in
the middle of the stack, and rebasing, with few real issues. (Not in
this case for licensing reasons, but so there's a clear chain of who
wrote what, and what was applied to what).
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2010-01-05 11:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 7:24 Joel Reymont
2010-01-05 8:32 ` [Caml-list] " Gabriel Kerneis
2010-01-05 8:41 ` Alain Frisch
2010-01-05 10:04 ` Jon Harrop
2010-01-05 11:08 ` Richard Jones [this message]
2010-01-05 14:57 ` Damien Doligez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100105110837.GC9256@annexia.org \
--to=rich@annexia.org \
--cc=caml-list@yquem.inria.fr \
--cc=jon@ffconsultancy.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox