From: Al Viro <viro@ftp.linux.org.uk>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org
Subject: Re: [PATCH 2/3] m68k: compile fix - ADBREQ_RAW missing declaration
Date: Thu, 15 Dec 2005 17:47:25 +0000 [thread overview]
Message-ID: <20051215174725.GZ27946@ftp.linux.org.uk> (raw)
In-Reply-To: <20051215171645.GY27946@ftp.linux.org.uk>
On Thu, Dec 15, 2005 at 05:16:45PM +0000, Al Viro wrote:
> So who should I put as the author? You or Geert (or whatever attributions
> might have been in said big patch)? Incidentally, ADBREQ_RAW had leaked
> into mainline (sans definition) in 2.3.45-pre2, which was Feb 13 2000, i.e.
> more than 1.5 year before your commit, so there's quite a chunk of history
> missing...
>
> I'm serious, BTW - I certainly would have no problem preserving attribution,
> but it simply hadn't been there. CVS logs are only as good as the data
> being put there by committers...
With some archaeology... It looks like drivers/macintosh part is from
Geert (with chunks from benh? not sure) circa Dec 2000; adb.h is a missing
piece of earlier patch (one that had leaked in Feb 2000, $DEITY knowns how
much older it is)...
next prev parent reply other threads:[~2005-12-15 17:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 8:55 [PATCH 2/3] m68k: compile fix - ADBREQ_RAW missing declaration Al Viro
2005-12-15 12:00 ` Roman Zippel
2005-12-15 17:16 ` Al Viro
2005-12-15 17:47 ` Al Viro [this message]
2005-12-15 17:54 ` Geert Uytterhoeven
2005-12-16 1:21 ` Finn Thain
2005-12-15 17:51 ` Roman Zippel
2005-12-15 17:55 ` Al Viro
2005-12-15 18:00 ` Geert Uytterhoeven
2005-12-15 18:14 ` Al Viro
2005-12-15 18:58 ` Al Viro
2005-12-15 20:05 ` Brad Boyer
2005-12-22 5:06 ` Al Viro
2005-12-25 2:26 ` Brad Boyer
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=20051215174725.GZ27946@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=zippel@linux-m68k.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).