All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] [PATCH 01/18] lustre: grant: add support for OBD_CONNECT_GRANT_PARAM
Date: Mon, 23 Jul 2018 10:36:12 +1000	[thread overview]
Message-ID: <87bmayrdoj.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <alpine.LFD.2.21.1807061528170.15728@casper.infradead.org>

On Fri, Jul 06 2018, James Simmons wrote:

>> ?On 7/2/18, 6:25 PM, "lustre-devel on behalf of James Simmons" <lustre-devel-bounces at lists.lustre.org on behalf of jsimmons@infradead.org> wrote:
>> 
>>     From: Johann Lombardi <jlombardi@whamcloud.com>
>>     Signed-off-by: Johann Lombardi <jlombardi@whamcloud.com>
>>     Signed-off-by: Jinshan Xiong <jinshan.xiong@gmail.com>
>>     WC-bug-id: https://jira.whamcloud.com/browse/2049
>>     Reviewed-on: http://review.whamcloud.com/7793
>>     Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
>>     Reviewed-by: Nathaniel Clark <nathaniel.l.clark@intel.com>
>>  
>> James, can you fix this up?  I'm not sure how historical patches should be attributed, but Johann's address seems
>> wrong.
>> 
>> From should be attributed to Johann Lombardi <johann.lombardi@intel.com> .  Also, the Bug URL should be
>> https://jira.whamcloud.com/browse/LU-2049 .
>
> This is tricky one. The reason I updated the email address to avoid 
> bouncing emails.

I would recommend never trying to update email addresses.  The kernel
history is full of addresses that are no longer valid.
Discussion of patches should happen on lists, and interested parties
should subscribe to the lists.  If someone wants to particularly see
emails sent to some old address of their's it should be easy enough to
add some filtering.  If you particularly want to contact the author of
some old patch, it is unlikely to take to much searching to find a valid
address (just ask on the email list - someone is bound to know).

Bounces are a little bit annoying, but so is spam - we just learn ways
to deal with it.

For this particular patch I've restored the addresses from the original
patch, even though I know some of them are no longer valid.  They were
valid when the review was done, and the effectively give credit to the
company which paid for the review.  I won't bother the rest though.

Thanks,
NeilBrown


> Also this allows the original author the chance to
> still reply. Does that seem reasonable? It is still in the air for
> some people what their email address is to me. Ah you are right I
> dropped the s. Its should be https://jira.whamcloud.com/....
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20180723/2d64cee1/attachment.sig>

  parent reply	other threads:[~2018-07-23  0:36 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02 23:24 [lustre-devel] [PATCH 00/18] lustre: missing updates from lustre 2.9 James Simmons
2018-07-02 23:24 ` [lustre-devel] [PATCH 01/18] lustre: grant: add support for OBD_CONNECT_GRANT_PARAM James Simmons
2018-07-03  3:04   ` NeilBrown
2018-07-03 12:43     ` Patrick Farrell
2018-07-03 21:59       ` NeilBrown
2018-07-06  4:02   ` Cory Spitz
2018-07-06 14:28     ` James Simmons
2018-07-06 14:29     ` James Simmons
2018-07-06 15:12       ` Andreas Dilger
2018-07-06 15:50         ` James Simmons
2018-07-23  0:36       ` NeilBrown [this message]
2018-07-02 23:24 ` [lustre-devel] [PATCH 02/18] lustre: ladvise: Add feature of giving file access advices James Simmons
2018-07-03  3:32   ` NeilBrown
2018-07-05 22:01     ` James Simmons
2018-07-02 23:24 ` [lustre-devel] [PATCH 03/18] lustre: fileset: add fileset mount support James Simmons
2018-07-03  3:52   ` NeilBrown
2018-07-02 23:24 ` [lustre-devel] [PATCH 04/18] lustre: obd: rename md_getstatus() to md_get_root() James Simmons
2018-07-02 23:24 ` [lustre-devel] [PATCH 05/18] lustre: llite: fast read implementation James Simmons
2018-07-03  4:10   ` NeilBrown
2018-07-03 12:46     ` Patrick Farrell
2018-07-03 22:03       ` NeilBrown
2018-07-02 23:24 ` [lustre-devel] [PATCH 06/18] lustre: obd: reserve connection flag OBD_CONNECT2_FILE_SECCTX James Simmons
2018-07-03  4:20   ` NeilBrown
2018-07-02 23:24 ` [lustre-devel] [PATCH 07/18] lustre: llite: restore fd_och when putting lease James Simmons
2018-07-02 23:24 ` [lustre-devel] [PATCH 08/18] lustre: security: send file security context for creates James Simmons
2018-07-03  4:26   ` NeilBrown
2018-07-02 23:24 ` [lustre-devel] [PATCH 09/18] lustre: llite: ladvise protocol changes James Simmons
2018-07-02 23:24 ` [lustre-devel] [PATCH 10/18] lustre: ladvise: Add willread advice support for ladvise James Simmons
2018-07-02 23:24 ` [lustre-devel] [PATCH 11/18] lustre: osc: max_pages_per_rpc should be chunk size aligned James Simmons
2018-07-02 23:24 ` [lustre-devel] [PATCH 12/18] lustre: ladvise: Add dontneed advice support for ladvise James Simmons
2018-07-02 23:24 ` [lustre-devel] [PATCH 13/18] lustre: ptlrpc: properly set "rq_xid" for 4MB IO James Simmons
2018-07-02 23:24 ` [lustre-devel] [PATCH 14/18] lustre: obd: add callback for llog_cat_process_or_fork James Simmons
2018-07-02 23:24 ` [lustre-devel] [PATCH 15/18] lustre: mount: fix lmd_parse() to handle new delimiters James Simmons
2018-07-02 23:24 ` [lustre-devel] [PATCH 16/18] lustre: libcfs: restore original behavior in cfs_str2num_check James Simmons
2018-07-03  4:45   ` NeilBrown
2018-07-05 22:50     ` James Simmons
2018-07-02 23:24 ` [lustre-devel] [PATCH 17/18] lustre: ldlm: reduce mem footprint of ldlm_resource James Simmons
2018-07-02 23:24 ` [lustre-devel] [PATCH 18/18] lustre: update version to 2.8.99 James Simmons
2018-07-03 21:46   ` Andreas Dilger
2018-07-05 22:53     ` James Simmons
2018-07-03  4:57 ` [lustre-devel] [PATCH 00/18] lustre: missing updates from lustre 2.9 NeilBrown

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=87bmayrdoj.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=lustre-devel@lists.lustre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.