From: Eric Sandeen <sandeen@redhat.com>
To: Christoph Hellwig <hch@infradead.org>,
Dave Chinner <david@fromorbit.com>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] misc: remove COPYING from doc/ Makefile
Date: Tue, 31 Jul 2018 10:36:05 -0500 [thread overview]
Message-ID: <00916b67-50bf-18b0-72b5-004f546659f0@redhat.com> (raw)
In-Reply-To: <20180731080825.GA16028@infradead.org>
On 7/31/18 3:08 AM, Christoph Hellwig wrote:
> On Tue, Jul 31, 2018 at 06:06:46PM +1000, Dave Chinner wrote:
>> Sorry, what? I added that as part of my spdx conversion patch. That
>> patch also removed the COPYING file.
>>
>> How did these changes get merged? I sent a pull request to convert
>> everything in xfsprogs and that had all the correct conversions and
>> documentation in it. here's the pull request:
>>
>> https://marc.info/?l=linux-xfs&m=152948738523911&w=2
>>
>> and you can see from the diffstat it did all this stuff...
>
> Ok. I looked for license info in master but that didn't have the
> whole conversion. That master vs for-next think in the userspace
> tools keeps on confusing me..
>
Sorry about that.
I can rethink it if needed, when I started this gig I was keeping
everything in rebaseable for-next because I feared egregious mistakes.
That's still possible but I'd like to think I'm a little better at it now ;)
-Eric
prev parent reply other threads:[~2018-07-31 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 3:41 [PATCH] misc: remove COPYING from doc/ Makefile Eric Sandeen
2018-07-31 3:45 ` Darrick J. Wong
2018-07-31 7:43 ` Christoph Hellwig
2018-07-31 8:06 ` Dave Chinner
2018-07-31 8:08 ` Christoph Hellwig
2018-07-31 15:36 ` Eric Sandeen [this message]
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=00916b67-50bf-18b0-72b5-004f546659f0@redhat.com \
--to=sandeen@redhat.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.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).