From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jaroslav Kysela <perex@perex.cz>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Takashi Iwai <tiwai@suse.de>,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [ALSA PATCH] alsa-git merge request
Date: Fri, 1 Feb 2008 10:24:35 +1100 (EST) [thread overview]
Message-ID: <alpine.LFD.1.00.0802011019460.17442@www.l.google.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0801311800290.6131@tm8103.perex-int.cz>
On Thu, 31 Jan 2008, Jaroslav Kysela wrote:
>
> Linus, please pull from [the linus branch at]:
>
> master.kernel.org:/pub/scm/linux/kernel/git/perex/alsa.git linus
Hmm. This has a number of commits that have a questionable sign-off
history (I complained about the same thing for the networking code).
Namely you cannot follow the path from "author" -> "committer" through the
sign-offs.
The reason seems to be that you are using some automatic service for your
hg/git gateway, and your committer information gets corrupted by that.
Please don't do this. I realize that Sign-offs don't always exist for the
whole path - we do take one-liners or otherwise known-ok patches from
sources without the sign-off of the author (ie not the normal (a) case for
the initial sign-off) - but the *normal* case should be that the whole
path from author->committer should be covered.
There is absolutely zero value in an automated "committer" field. Please
fix your hg gateway to not do this kind of crap.
Linus
next prev parent reply other threads:[~2008-01-31 23:25 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 17:04 Jaroslav Kysela
2008-01-31 23:24 ` Linus Torvalds [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-10 12:12 Jaroslav Kysela
2008-10-11 10:21 ` Takashi Iwai
2008-07-14 9:09 Jaroslav Kysela
2008-08-24 21:30 ` Guillaume Chazarain
2008-08-25 5:50 ` Takashi Iwai
2008-08-25 21:36 ` Guillaume Chazarain
2008-08-25 22:43 ` Guillaume Chazarain
2008-08-26 5:59 ` Takashi Iwai
2008-08-26 21:10 ` Guillaume Chazarain
2008-08-27 6:02 ` Takashi Iwai
2007-11-19 18:35 Jaroslav Kysela
2007-11-20 6:48 ` Takashi Iwai
2007-11-20 19:20 ` Jaroslav Kysela
2007-10-23 6:14 Jaroslav Kysela
2007-10-16 15:08 Jaroslav Kysela
2007-07-20 9:39 Jaroslav Kysela
2007-05-31 9:07 Jaroslav Kysela
2007-05-16 9:50 Jaroslav Kysela
2007-05-09 9:59 Jaroslav Kysela
2007-05-03 12:51 Jaroslav Kysela
2007-03-14 7:28 Jaroslav Kysela
2007-03-06 14:20 Jaroslav Kysela
2007-02-14 7:46 Jaroslav Kysela
2007-02-14 17:53 ` Linus Torvalds
2007-02-09 14:02 Jaroslav Kysela
2007-02-09 14:15 ` Takashi Iwai
2007-02-09 14:40 ` Jaroslav Kysela
2007-02-09 14:47 ` Takashi Iwai
2007-02-09 15:00 ` Takashi Iwai
2007-02-09 15:30 ` Jaroslav Kysela
2007-02-09 15:58 ` Linus Torvalds
2007-02-09 16:07 ` Jaroslav Kysela
2007-01-23 8:31 Jaroslav Kysela
2007-01-09 14:04 Jaroslav Kysela
2006-12-20 8:52 Jaroslav Kysela
2006-12-15 7:52 Jaroslav Kysela
2006-12-15 8:13 ` Andrew Morton
2006-12-15 8:17 ` Andrew Morton
2006-12-15 8:44 ` Jaroslav Kysela
2006-12-15 8:45 ` Jaroslav Kysela
2006-12-15 16:00 ` Linus Torvalds
2006-11-28 14:11 Jaroslav Kysela
2006-10-22 9:09 Jaroslav Kysela
2006-10-06 18:27 Jaroslav Kysela
2006-09-23 9:23 Jaroslav Kysela
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.LFD.1.00.0802011019460.17442@www.l.google.com \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®