List for cgit developers and users
 help / color / mirror / Atom feed
From: john at keeping.me.uk (John Keeping)
Subject: [PATCH 1/1] ui-shared: Use CRLF in HTTP headers as per RFC 7230
Date: Wed, 11 May 2016 20:57:52 +0100	[thread overview]
Message-ID: <20160511195752.GJ4296@serenity.lan> (raw)
In-Reply-To: <20160511193824.GB9158@partyvan.eu>

On Wed, May 11, 2016 at 07:38:24PM +0000, Juuso Lapinlampi wrote:
> On Wed, May 11, 2016 at 07:30:49PM +0100, John Keeping wrote:
> > Missing sign-off; see http://developercertificate.org/ for what this
> > means.
> 
> I am aware, but small changes like these are not generally recognized to
> fit the threshold of originality for copyright protection. Thus, the
> idea of Signed-off is quite often silly.

"generally recognized" is a bit nebulous, which is why a blanket policy
is safer as well as much simpler to police.


  reply	other threads:[~2016-05-11 19:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-11 17:48 wub
2016-05-11 18:30 ` john
2016-05-11 19:31   ` john
2016-05-11 19:38   ` wub
2016-05-11 19:57     ` john [this message]
2016-05-11 20:15       ` wub
2016-05-12 10:23         ` john
2016-05-12 15:45     ` Jason
2016-05-12 15:45 ` Jason

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=20160511195752.GJ4296@serenity.lan \
    --to=cgit@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).