From: Phillip Potter <email@example.com> To: Amir Goldstein <firstname.lastname@example.org> Cc: email@example.com, firstname.lastname@example.org, email@example.com Subject: Re: [RFC][PATCH v3 01/10] fs: common implementation of file type Date: Wed, 24 Oct 2018 10:56:01 +0100 [thread overview] Message-ID: <20181024095601.GA19974@pathfinder> (raw) In-Reply-To: <CAOQ4uxjyTtjPk1OaWCSKs3Larqog+vmqLSth1kKWdOA5oRTtAA@mail.gmail.com> On Wed, Oct 24, 2018 at 12:44:50PM +0300, Amir Goldstein wrote: > On Wed, Oct 24, 2018 at 12:31 PM Phillip Potter <firstname.lastname@example.org> wrote: > > > > On Wed, Oct 24, 2018 at 12:20:14PM +0300, Amir Goldstein wrote: > > > On Wed, Oct 24, 2018 at 11:21 AM Phillip Potter <email@example.com> wrote: > > > > Dear Amir, > > > > > > > > Yes, I applied each patch manually to my tree, fixed it up where needed, > > > > then after rebuilding and testing each one I committed it and regenerated > > > > each patch. Thank you very much for your advice, I will take it into > > > > account and make the necessary changes. In the meantime, do I add other > > > > tags in the order they are received also (such as Reviewed-by:) and am > > > > I safe to add these in when I re-send the patches with the changes you > > > > and others have suggested (or would that offend people that have > > > > offered the tags)? > > > > > > > > > > Reviewed-by before of after Signed-off-by. > > > I prefer Signed-off-by last which conceptually covers the entire patch, > > > the commit message including all the review tags that you may have added. > > > > > > Some developers add Reviewed-by after Signed-off-by signifying the > > > order that things happened, so choose your own preference. > > > > > > As a reviewer, and I speak only for myself, if I offered my Reviewed-by > > > I expect it to be removed if a future revision of the patch has changed > > > so I have an indication of patches that I need to re-review. > > > But if the patch changed very lightly, like small edits to commit message > > > and code nits in general, that would not invalidate my review. > > > When in doubt, you can always explicitly ask the reviewer. > > > > > > Thanks, > > > Amir. > > > > Dear Amir, > > > > Thanks - I am just going to fix up the commit messages as you suggested > > using git am etc. The content of the patches themselves will not change > > (until further feedback is received). > > > > Well, I did request to change some content (the location and the comment > above BUILD_BUG_ON section) which is relevant for several patches. > However, so far affected patched did not get any Reviewed-by. > > Thanks, > Amir. Sorry, I missed that bit at the end, was too keen to click through to the note about the alleged ext2 bug :-) I will make sure those changes are made as well. By location do you mean the location of the v3, v2, etc. stuff and your point about including it in the main [0/10] message rather than the patches themselves? Again, thank you for your feedback and for being patient with me, I really do appreciate it. Regards, Phil
next prev parent reply other threads:[~2018-10-24 9:56 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-23 20:19 Phillip Potter 2018-10-24 6:16 ` Amir Goldstein 2018-10-24 8:21 ` Phillip Potter 2018-10-24 9:20 ` Amir Goldstein 2018-10-24 9:31 ` Phillip Potter 2018-10-24 9:44 ` Amir Goldstein 2018-10-24 9:56 ` Phillip Potter [this message] 2018-10-24 10:06 ` Amir Goldstein 2018-10-24 12:37 ` Al Viro 2018-10-24 13:02 ` Theodore Y. Ts'o 2018-10-24 14:41 ` Amir Goldstein 2018-10-25 11:20 ` Jan Kara
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=20181024095601.GA19974@pathfinder \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [RFC][PATCH v3 01/10] fs: common implementation of file type' \ /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
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).