From: Dan Aloni <da-x@monatomic.org>
To: Oleg Verych <olecom@flower.upol.cz>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] automatic CC generation for patch submission
Date: Sat, 30 Jun 2007 13:26:01 +0300 [thread overview]
Message-ID: <20070630102601.GA24044@localdomain> (raw)
In-Reply-To: <20070630102246.GF10398@flower.upol.cz>
On Sat, Jun 30, 2007 at 12:22:46PM +0200, Oleg Verych wrote:
> > Right, however many patches don't map to bug reports and don't
> > need the heavy use of BTS. This suggestion is mainly for the
> > improvement of peer review concerning code changes submitted
> > by people who are not the maintainers.
>
> Unfortunately you didn't listen, OK, just two messages:
>
> <http://permalink.gmane.org/gmane.linux.kernel/544898>
> <http://permalink.gmane.org/gmane.linux.kernel/545112>
>
> As you will see, nobody cares about comprehensive
> patches/tests/bugs/testers/developers *tracking* system.
>
> And don't limit yourself to fast conclusions. Thanks.
I am not proposing a comprehensive tracking system. I think
you are taking my intentions quite off-course.
--
Dan Aloni
XIV LTD, http://www.xivstorage.com
da-x (at) monatomic.org, dan (at) xiv.co.il
next prev parent reply other threads:[~2007-06-30 10:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 2:34 [RFC] automatic CC generation for patch submission Dan Aloni
2007-06-30 2:51 ` Kok, Auke
2007-06-30 3:10 ` Satyam Sharma
2007-06-30 3:29 ` Satyam Sharma
2007-06-30 9:54 ` Andrew Morton
2007-06-30 10:47 ` Dan Aloni
2007-06-30 16:32 ` Andrew Morton
2007-06-30 17:20 ` Adrian Bunk
2007-06-30 17:21 ` Dan Aloni
2007-06-30 14:33 ` Kok, Auke
2007-06-30 3:01 ` Oleg Verych
2007-06-30 3:08 ` Dan Aloni
2007-06-30 10:22 ` Oleg Verych
2007-06-30 10:26 ` Dan Aloni [this message]
2007-06-30 11:03 ` Oleg Verych
2007-06-30 4:01 ` Adrian Bunk
2007-06-30 9:47 ` Dan Aloni
2007-06-30 12:26 ` Adrian Bunk
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=20070630102601.GA24044@localdomain \
--to=da-x@monatomic.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olecom@flower.upol.cz \
/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