All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: cluster-devel <cluster-devel@redhat.com>, linux-kernel@vger.kernel.org
Subject: Regression in my latest GFS2 pull request
Date: Fri, 5 May 2017 12:31:11 -0400 (EDT)	[thread overview]
Message-ID: <1467104190.4487433.1494001871746.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1764624605.4463543.1494001455155.JavaMail.zimbra@redhat.com>

Hi Linus,

I see that you haven't processed my latest GFS2 pull request.

Today I found a regression in one of those patches. I've written,
tested, and posted a patch to cluster-devel to fix the problem,
and I'd like to get it into this merge window because it's severe.
(You can't unmount a gfs2 file system after withdraw due to errors).

My question is: How would you like me to handle it?

Push the new patch, tag it, and do a second pull request?
Wait until you've processed the first pull request, then do so?
Or is there a better way?

Regards,

Bob Peterson

WARNING: multiple messages have this Message-ID (diff)
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Regression in my latest GFS2 pull request
Date: Fri, 5 May 2017 12:31:11 -0400 (EDT)	[thread overview]
Message-ID: <1467104190.4487433.1494001871746.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1764624605.4463543.1494001455155.JavaMail.zimbra@redhat.com>

Hi Linus,

I see that you haven't processed my latest GFS2 pull request.

Today I found a regression in one of those patches. I've written,
tested, and posted a patch to cluster-devel to fix the problem,
and I'd like to get it into this merge window because it's severe.
(You can't unmount a gfs2 file system after withdraw due to errors).

My question is: How would you like me to handle it?

Push the new patch, tag it, and do a second pull request?
Wait until you've processed the first pull request, then do so?
Or is there a better way?

Regards,

Bob Peterson



       reply	other threads:[~2017-05-05 16:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1764624605.4463543.1494001455155.JavaMail.zimbra@redhat.com>
2017-05-05 16:31 ` Bob Peterson [this message]
2017-05-05 16:31   ` [Cluster-devel] Regression in my latest GFS2 pull request Bob Peterson

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=1467104190.4487433.1494001871746.JavaMail.zimbra@redhat.com \
    --to=rpeterso@redhat.com \
    --cc=cluster-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.