From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GIT PULL] dlm updates for 6.0
Date: Mon, 1 Aug 2022 10:50:28 -0500 [thread overview]
Message-ID: <20220801155028.GA12328@redhat.com> (raw)
In-Reply-To: <CAHk-=wgCi2LLzSJg_7nRs+nQbVgT8HwEKzjMae_4geVCA+1SNg@mail.gmail.com>
On Mon, Aug 01, 2022 at 08:46:24AM -0700, Linus Torvalds wrote:
> On Mon, Aug 1, 2022 at 7:43 AM David Teigland <teigland@redhat.com> wrote:
> >
> > (You can ignore the premature 5.20 pull request from some weeks ago.)
>
> Gaah. That was the first thing I pulled this morning because it was
> the earliest.
>
> And apparently you've rebased, so I can't even just pull on top.
>
> Gaah. Now I'll have to go back and re-do everything I've done this morning.
>
> PLEASE don't do things like this to me. If you know you are going to
> re-do a pull request, let me know early, so that I don't pull the old
> one.
Very sorry about that. (The obvious change there was updating the version
numbers in the deprecation messages to 6.2, and I should have just sent a
seprate patch to fix those up.)
Dave
WARNING: multiple messages have this Message-ID (diff)
From: David Teigland <teigland@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, cluster-devel@redhat.com
Subject: Re: [GIT PULL] dlm updates for 6.0
Date: Mon, 1 Aug 2022 10:50:28 -0500 [thread overview]
Message-ID: <20220801155028.GA12328@redhat.com> (raw)
In-Reply-To: <CAHk-=wgCi2LLzSJg_7nRs+nQbVgT8HwEKzjMae_4geVCA+1SNg@mail.gmail.com>
On Mon, Aug 01, 2022 at 08:46:24AM -0700, Linus Torvalds wrote:
> On Mon, Aug 1, 2022 at 7:43 AM David Teigland <teigland@redhat.com> wrote:
> >
> > (You can ignore the premature 5.20 pull request from some weeks ago.)
>
> Gaah. That was the first thing I pulled this morning because it was
> the earliest.
>
> And apparently you've rebased, so I can't even just pull on top.
>
> Gaah. Now I'll have to go back and re-do everything I've done this morning.
>
> PLEASE don't do things like this to me. If you know you are going to
> re-do a pull request, let me know early, so that I don't pull the old
> one.
Very sorry about that. (The obvious change there was updating the version
numbers in the deprecation messages to 6.2, and I should have just sent a
seprate patch to fix those up.)
Dave
next prev parent reply other threads:[~2022-08-01 15:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 14:43 [Cluster-devel] [GIT PULL] dlm updates for 6.0 David Teigland
2022-08-01 14:43 ` David Teigland
2022-08-01 15:46 ` [Cluster-devel] " Linus Torvalds
2022-08-01 15:46 ` Linus Torvalds
2022-08-01 15:50 ` David Teigland [this message]
2022-08-01 15:50 ` David Teigland
2022-08-01 15:56 ` [Cluster-devel] " David Teigland
2022-08-01 15:56 ` David Teigland
2022-08-01 16:17 ` [Cluster-devel] " Linus Torvalds
2022-08-01 16:17 ` Linus Torvalds
2022-08-01 16:51 ` [Cluster-devel] " David Teigland
2022-08-01 16:51 ` David Teigland
2022-08-01 16:18 ` [Cluster-devel] " pr-tracker-bot
2022-08-01 16:18 ` pr-tracker-bot
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=20220801155028.GA12328@redhat.com \
--to=teigland@redhat.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.