All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: John Lane <grub@jelmail.com>, Daniel Kiper <dkiper@net-space.pl>
Cc: grub-devel@gnu.org
Subject: Re: [PATCH 1/7] Cryptomount support LUKS detached header
Date: Wed, 21 Mar 2018 08:23:57 +0100	[thread overview]
Message-ID: <1521617037.7171.726.camel@users.sourceforge.net> (raw)
In-Reply-To: <593f8408-d54b-ab12-2660-f15d55418acb@jelmail.com>

[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]

Dear John,


Am Mittwoch, den 14.03.2018, 19:00 +0000 schrieb John Lane:
> On 14/03/18 13:05, Daniel Kiper wrote:
> > On Wed, Mar 14, 2018 at 09:44:58AM +0000, John Lane wrote:
> > > From: John Lane <john@lane.uk.net>
> > 
> > I have just skimmed through the series. First of all, most if not
> > all patches beg for full blown commit messages. Just vague statements
> > in the subject are insufficient for me. And please add patch 0 which
> > introduces the series. git send-email --compose is your friend.
> 
> Sorry Daniel, this isn't something I do that often - submitting patches
> to ML. Do you want me to resubmit them again, or is the below ok for you ?

[…]

Thank you very much for submitting these patches for review. Judging
from the other comments, it looks like, you are going to send an
updated series anyway, so I guess, you can wait until then, though
expect another round then.

I do not know, how well you are versed with git, but it’d be great, if
you added your messages below as “real” commit messages. `git rebase -i
origin/master` should do that for you. Just replace *pick* by *r*, for
*r*eword, and add the commit messages there.

So, as testing the review changes will take some time, I suggest you
try to resend the patch series as soon as possible to get as much
reviews as possible, so you can test everything, when you get to it.


Thanks,

Paul

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2018-03-21  7:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14  9:44 [PATCH 1/7] Cryptomount support LUKS detached header John Lane
2018-03-14  9:44 ` [PATCH 2/7] Cryptomount support key files John Lane
2018-03-17 11:10   ` TJ
2018-03-18 20:29     ` John Lane
2018-03-14  9:45 ` [PATCH 3/7] cryptomount luks allow multiple passphrase attempts John Lane
2018-03-17 11:10   ` TJ
2018-03-18 20:30     ` John Lane
2018-03-14  9:45 ` [PATCH 4/7] Cryptomount support plain dm-crypt John Lane
2018-03-14  9:45 ` [PATCH 5/7] Cryptomount support for hyphens in UUID John Lane
2018-03-14  9:45 ` [PATCH 6/7] Retain constness of parameters John Lane
2018-03-14  9:45 ` [PATCH 7/7] Add support for using a whole device as a keyfile John Lane
2018-03-14 13:05 ` [PATCH 1/7] Cryptomount support LUKS detached header Daniel Kiper
2018-03-14 19:00   ` John Lane
2018-03-21  7:23     ` Paul Menzel [this message]
2018-03-22 12:38     ` Daniel Kiper
2018-03-22 14:22       ` TJ
2018-03-26 13:10         ` John Lane
2018-03-26 14:42           ` Daniel Kiper
2018-03-17 11:09 ` TJ
2018-03-18 20:29   ` John Lane

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=1521617037.7171.726.camel@users.sourceforge.net \
    --to=paulepanter@users.sourceforge.net \
    --cc=dkiper@net-space.pl \
    --cc=grub-devel@gnu.org \
    --cc=grub@jelmail.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 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.