From: Andreas Ericsson <ae@op5.se>
To: Junio C Hamano <gitster@pobox.com>
Cc: Nelson Benitez Leon <nelsonjesus.benitez@seap.minhap.es>,
git@vger.kernel.org
Subject: Re: [PATCH] documentation: fix alphabetic ordered list for git-rebase man page
Date: Mon, 26 Mar 2012 13:57:43 +0200 [thread overview]
Message-ID: <4F7059B7.8080406@op5.se> (raw)
In-Reply-To: <7vd383t8vp.fsf@alter.siamese.dyndns.org>
On 03/23/2012 08:28 PM, Junio C Hamano wrote:
> Thanks; sign-off?
Having just checked up on this myself for a project I maintain and
was sent a patch without signoff (we shamelessly stole git.git's
meaning of signoffs), I have it on a copyright lawyer's word that
you can safely forge the sign-off for anything that provides a
bugfix without adding a new way of doing things, since only changes
that carry a certain amount of originality can be copyright protected.
Fixing an alphabetic ordering is too trivial to grant the author of
the fix any right to the resulting work, as are typo-, grammar and
one-line syntactical fixes (adding missing braces, etc), and therefore
they do not need to sign off on the fact that they have a right to
give others the right to use that work, since they in fact do not have
the right to restrict others from using it in the first place.
Just thought I'd throw that out there in case you, like I did, run into
useful patches you dare not use because the original author gets hard
to contact all of a sudden.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
next prev parent reply other threads:[~2012-03-26 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 11:31 [PATCH] documentation: fix alphabetic ordered list for git-rebase man page Nelson Benitez Leon
2012-03-23 19:28 ` Junio C Hamano
2012-03-26 11:57 ` Andreas Ericsson [this message]
2012-03-26 17:32 ` Junio C Hamano
2012-03-27 10:40 ` Nelson Benitez Leon
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=4F7059B7.8080406@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nelsonjesus.benitez@seap.minhap.es \
/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;
as well as URLs for NNTP newsgroup(s).