From: Jens Axboe <axboe@kernel.dk>
To: "Bean Huo (beanhuo)" <beanhuo@micron.com>,
Bart Van Assche <bvanassche@acm.org>,
"Luca Porzio (lporzio)" <lporzio@micron.com>,
Luis Chamberlain <mcgrof@kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>
Cc: "Matias Bjørling" <Matias.Bjorling@wdc.com>,
"Javier González" <javier.gonz@samsung.com>,
"Damien Le Moal" <Damien.LeMoal@wdc.com>,
"Adam Manzanares" <a.manzanares@samsung.com>,
"Keith Busch" <Keith.Busch@wdc.com>,
"Johannes Thumshirn" <Johannes.Thumshirn@wdc.com>,
"Naohiro Aota" <Naohiro.Aota@wdc.com>,
"Pankaj Raghav" <pankydev8@gmail.com>,
"Kanchan Joshi" <joshi.k@samsung.com>,
"Nitesh Shetty" <nj.shetty@samsung.com>
Subject: Re: [EXT] [LSF/MM/BPF BoF] BoF for Zoned Storage
Date: Tue, 15 Mar 2022 13:16:58 -0600 [thread overview]
Message-ID: <72af146c-3cbf-73ce-4788-d999518d47a4@kernel.dk> (raw)
In-Reply-To: <PH0PR08MB7889314A7E3C8FEC1E7A491CDB109@PH0PR08MB7889.namprd08.prod.outlook.com>
On 3/15/22 1:04 PM, Bean Huo (beanhuo) wrote:
>> -----Original Message-----
>> From: Jens Axboe <axboe@kernel.dk>
>> Sent: Tuesday, March 15, 2022 7:49 PM
>> To: Bean Huo (beanhuo) <beanhuo@micron.com>; Bart Van Assche
>> <bvanassche@acm.org>; Luca Porzio (lporzio) <lporzio@micron.com>; Luis
>> Chamberlain <mcgrof@kernel.org>; linux-block@vger.kernel.org; linux-
>> fsdevel@vger.kernel.org; lsf-pc@lists.linux-foundation.org
>> Cc: Matias Bj?rling <Matias.Bjorling@wdc.com>; Javier Gonz?lez
>> <javier.gonz@samsung.com>; Damien Le Moal <Damien.LeMoal@wdc.com>;
>> Adam Manzanares <a.manzanares@samsung.com>; Keith Busch
>> <Keith.Busch@wdc.com>; Johannes Thumshirn <Johannes.Thumshirn@wdc.com>;
>> Naohiro Aota <Naohiro.Aota@wdc.com>; Pankaj Raghav
>> <pankydev8@gmail.com>; Kanchan Joshi <joshi.k@samsung.com>; Nitesh Shetty
>> <nj.shetty@samsung.com>
>> Subject: Re: [EXT] [LSF/MM/BPF BoF] BoF for Zoned Storage
All of this is duplicated info too, it just makes your emails have poor
signal to noise ratio...
>> CAUTION: EXTERNAL EMAIL. Do not click links or open attachments unless you
>> recognize the sender and were expecting this message.
Same
>>> Micron Confidential
>>
>>>
>>> Micron Confidential
>>
>> Must be very confidential if it needs two?
>>
>> Please get rid of these useless disclaimers in public emails, they make ZERO sense.
>>
>
> Sorry for that. They are added by outlook automatically, seems I can
> turn it off, let me see if this email has this message.
In general, advise for open source or open list emails:
- Don't include any "Foo company confidential", which by definition is
nonsensical because the email is sent out publically.
- Wrap lines in emails. Wrapping them at 74 chars or something like that
makes them a LOT easier to read, and means I don't have to wrap your
replies when I reply.
- Don't include huge headers of who got the email. That part is in the
email headers already, and it's just noise in the body of the email.
- Trim replies! Nothing worse than browsing page after page of just
quoted text to get to the meat of it.
That's just the basics, but it goes a long way towards making email a
more useful medium. And making the sender/company look like they
understand how open source collaborations and communication works.
--
Jens Axboe
next prev parent reply other threads:[~2022-03-15 19:17 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 0:56 [LSF/MM/BPF BoF] BoF for Zoned Storage Luis Chamberlain
2022-03-03 1:03 ` Luis Chamberlain
2022-03-03 1:33 ` Bart Van Assche
2022-03-03 4:31 ` Matias Bjørling
2022-03-03 5:21 ` Adam Manzanares
2022-03-03 5:32 ` Javier González
2022-03-03 6:29 ` Javier González
2022-03-03 7:54 ` Pankaj Raghav
2022-03-03 9:49 ` Damien Le Moal
2022-03-03 14:55 ` Adam Manzanares
2022-03-03 15:22 ` Damien Le Moal
2022-03-03 17:10 ` Adam Manzanares
2022-03-03 19:51 ` Matias Bjørling
2022-03-03 20:18 ` Adam Manzanares
2022-03-03 21:08 ` Javier González
2022-03-03 21:33 ` Matias Bjørling
2022-03-04 20:12 ` Luis Chamberlain
2022-03-06 23:54 ` Damien Le Moal
2022-03-03 16:12 ` Himanshu Madhani
2022-03-03 7:21 ` Hannes Reinecke
2022-03-03 8:55 ` Damien Le Moal
2022-03-03 7:38 ` Kanchan Joshi
2022-03-03 8:43 ` Johannes Thumshirn
2022-03-03 18:20 ` Viacheslav Dubeyko
2022-03-04 0:10 ` Dave Chinner
2022-03-04 22:10 ` Luis Chamberlain
2022-03-04 22:42 ` Dave Chinner
2022-03-04 22:55 ` Luis Chamberlain
2022-03-05 7:33 ` Javier González
2022-03-07 7:12 ` Dave Chinner
2022-03-07 10:27 ` Matias Bjørling
2022-03-07 11:29 ` Javier González
2022-03-11 0:49 ` Luis Chamberlain
2022-03-11 6:07 ` Christoph Hellwig
2022-03-11 20:31 ` Luis Chamberlain
2022-03-07 13:55 ` James Bottomley
2022-03-07 14:35 ` Javier González
2022-03-07 15:15 ` Keith Busch
2022-03-07 15:28 ` Javier González
2022-03-07 20:42 ` Damien Le Moal
2022-03-11 7:21 ` Javier González
2022-03-11 7:39 ` Damien Le Moal
2022-03-11 7:42 ` Christoph Hellwig
2022-03-11 7:53 ` Javier González
2022-03-11 8:46 ` Christoph Hellwig
2022-03-11 8:59 ` Javier González
2022-03-12 8:03 ` Damien Le Moal
2022-03-07 0:07 ` Damien Le Moal
2022-03-06 23:56 ` Damien Le Moal
2022-03-07 15:44 ` Luis Chamberlain
2022-03-07 16:23 ` Johannes Thumshirn
2022-03-07 16:36 ` Luis Chamberlain
2022-03-15 18:08 ` [EXT] " Luca Porzio (lporzio)
2022-03-15 18:39 ` Bart Van Assche
2022-03-15 18:47 ` Bean Huo (beanhuo)
2022-03-15 18:49 ` Jens Axboe
2022-03-15 19:04 ` Bean Huo (beanhuo)
2022-03-15 19:16 ` Jens Axboe [this message]
2022-03-15 19:59 ` Bart Van Assche
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=72af146c-3cbf-73ce-4788-d999518d47a4@kernel.dk \
--to=axboe@kernel.dk \
--cc=Damien.LeMoal@wdc.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=Keith.Busch@wdc.com \
--cc=Matias.Bjorling@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=a.manzanares@samsung.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=javier.gonz@samsung.com \
--cc=joshi.k@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lporzio@micron.com \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mcgrof@kernel.org \
--cc=nj.shetty@samsung.com \
--cc=pankydev8@gmail.com \
/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