From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Richard Weinberger <richard@nod.at>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: Re: linux-next: Fixes tags need some work in the mtd tree
Date: Tue, 7 May 2019 06:58:08 +1000 [thread overview]
Message-ID: <20190507065808.342affcb@canb.auug.org.au> (raw)
In-Reply-To: <1062675236.47533.1557175510785.JavaMail.zimbra@nod.at>
[-- Attachment #1: Type: text/plain, Size: 268 bytes --]
Hi Richard,
On Mon, 6 May 2019 22:45:10 +0200 (CEST) Richard Weinberger <richard@nod.at> wrote:
>
> What is the suggest approach to fix that?
> Rebase and force-push?
It's probably not worth it, just remember for next time.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-05-06 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 20:40 linux-next: Fixes tags need some work in the mtd tree Stephen Rothwell
2019-05-06 20:45 ` Richard Weinberger
2019-05-06 20:58 ` Stephen Rothwell [this message]
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=20190507065808.342affcb@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=richard@nod.at \
/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;
as well as URLs for NNTP newsgroup(s).