linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Charlemagne Lasse <charlemagnelasse@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linuxfoundation.org>,
	Andrew Morton <akpm@linuxfoundation.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Philippe Ombredanne <pombredanne@nexb.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Christoph Hellwig <hch@lst.de>,
	Russell King <rmk+kernel@armlinux.org.uk>,
	Rob Herring <rob.herring@linaro.org>,
	Jonas Oberg <jonas@fsfe.org>, Joe Perches <joe@perches.com>,
	linux-xfs@vger.kernel.org,
	Kate Stewart <kstewart@linuxfoundation.org>,
	Carmen Bianca Bakker <carmenbianca@fsfe.org>
Subject: Re: [1/7] Documentation: Add license-rules.rst to describe how to properly identify file licenses
Date: Mon, 13 Nov 2017 14:26:04 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1711131424240.1851@nanos> (raw)
In-Reply-To: <CAFGhKbz3XRxjk85aj80Hy7BQ7gf5zLkfSdmJioXwAs+Zxi7nZA@mail.gmail.com>

On Mon, 13 Nov 2017, Charlemagne Lasse wrote:

> 2017-11-13 13:26 GMT+01:00 Thomas Gleixner <tglx@linutronix.de>:
> > On Mon, 13 Nov 2017, Charlemagne Lasse wrote:
> >> > +If a specific tool cannot handle the standard comment style, then the
> >> > +appropriate comment mechanism which the tool accepts shall be used.
> >>
> >> Most of the things sound good. But I really don't get the first-line
> >> thing and the C++ single line comments in C sources.
> >
> > That's been a decision from Linus and probably not going to change, even if
> > you argue in circles.
> 
> I always thought that Linus is the person reponsible for unfriendly
> responses. But ok, when it is not wanted to discuss anything then please
> ignore me.

That was not meant unfriendly. I merily tried to make it clear that it's a
decision which I'm pretty sure that it won't be changed. Feel free to
discuss it with Linus.

Thanks,

	tglx

  reply	other threads:[~2017-11-13 13:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-12 19:18 [patch 0/7] LICENSES: Add documentation and initial License files Thomas Gleixner
2017-11-12 19:18 ` [patch 1/7] Documentation: Add license-rules.rst to describe how to properly identify file licenses Thomas Gleixner
2017-11-12 19:54   ` Joe Perches
2017-11-12 19:57     ` Thomas Gleixner
2017-11-12 20:07   ` Jonathan Corbet
2017-11-12 20:19     ` Thomas Gleixner
2017-11-13 10:04   ` [1/7] " Charlemagne Lasse
2017-11-13 12:26     ` Thomas Gleixner
2017-11-13 12:40       ` Charlemagne Lasse
2017-11-13 13:26         ` Thomas Gleixner [this message]
2017-11-16 15:07   ` [patch 1/7] " Jonathan Corbet
2017-11-16 15:15     ` Jonas Oberg
2017-11-16 18:03       ` Thomas Gleixner
2017-11-17  7:37       ` Philippe Ombredanne
2017-11-17  8:57         ` Greg Kroah-Hartman
2017-11-17 10:53           ` Philippe Ombredanne
2017-11-17 12:29             ` Greg Kroah-Hartman
2017-11-12 19:18 ` [patch 2/7] LICENSES: Add the GPL 2.0 license Thomas Gleixner
2017-11-14 18:02   ` Rob Herring
2017-11-14 19:05     ` Greg Kroah-Hartman
2017-11-16 11:46   ` Jonas Oberg
2017-11-16 13:12     ` Thomas Gleixner
2017-11-12 19:18 ` [patch 3/7] LICENSES: Add the GPL 1.0 license Thomas Gleixner
2017-11-12 19:18 ` [patch 4/7] LICENSES: Add the BSD 2-clause "Simplified" license Thomas Gleixner
2017-11-12 19:18 ` [patch 5/7] LICENSES: Add the BSD 3-clause "New" or "Revised" License Thomas Gleixner
2017-11-12 19:18 ` [patch 6/7] LICENSES: Add the MIT license Thomas Gleixner
2017-11-12 19:18 ` [patch 7/7] LICENSES: Add Linux syscall note exception Thomas Gleixner
2017-11-12 20:02 ` [patch 0/7] LICENSES: Add documentation and initial License files Joe Perches
2017-11-12 20:55   ` Thomas Gleixner
2017-11-13 13:54 ` Philippe Ombredanne
2017-11-14 10:15 ` Russell King - ARM Linux

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=alpine.DEB.2.20.1711131424240.1851@nanos \
    --to=tglx@linutronix.de \
    --cc=akpm@linuxfoundation.org \
    --cc=carmenbianca@fsfe.org \
    --cc=charlemagnelasse@gmail.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=joe@perches.com \
    --cc=jonas@fsfe.org \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=pombredanne@nexb.com \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=rob.herring@linaro.org \
    --cc=torvalds@linuxfoundation.org \
    /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).