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 11:51:16 -0500 [thread overview]
Message-ID: <20220801165115.GC12328@redhat.com> (raw)
In-Reply-To: <CAHk-=wi07ue68JuYXDdPD-s93UTs0Tp0oAvdnyxS3zQQSosEOA@mail.gmail.com>
On Mon, Aug 01, 2022 at 09:17:30AM -0700, Linus Torvalds wrote:
> But again: please don't rebase stuff you have already exposed to
> others. It causes real issues. This was just one example of it.
>
> And if you *do* have to rebase for a real technical reason ("Oh, that
> was a disaster, it absolutely *must* be fixed"), please let involved
> people know asap.
>
> And a version number change is not a "huge disaster, must rebase".
Yep, thanks for the comments. For some reason this escaped the usual flags
that should have gone off in my head about rebasing.
Dave
next prev parent reply other threads:[~2022-08-01 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 14:43 [GIT PULL] dlm updates for 6.0 David Teigland
2022-08-01 15:46 ` Linus Torvalds
2022-08-01 15:50 ` David Teigland
2022-08-01 15:56 ` David Teigland
2022-08-01 16:17 ` Linus Torvalds
2022-08-01 16:51 ` David Teigland [this message]
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=20220801165115.GC12328@redhat.com \
--to=teigland@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox