From: Ian Campbell <ijc@hellion.org.uk>
To: Hector Martin <marcan@marcan.st>
Cc: Rob Herring <robh+dt@kernel.org>,
DTML <devicetree@vger.kernel.org>, Janne Grunau <j@jannau.net>,
Sven Peter <sven@svenpeter.dev>,
Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: Broken devicetree-rebasing history
Date: Mon, 14 Mar 2022 20:38:28 +0000 [thread overview]
Message-ID: <5406cf9c36cde3bc090365f96e5fdfde017af643.camel@hellion.org.uk> (raw)
In-Reply-To: <677bf0dcf6b17eb7fb5489524e0c4ac4ad450ff0.camel@hellion.org.uk>
On Sun, 2022-03-13 at 12:00 +0000, Ian Campbell wrote:
>
> Obviously this is going to involve a force push and a whole new pile of
> updated tags in the repo on kernel.org, I'll send an heads up to the
> list when I get as far as actually pushing.
Done.
Thanks again for the heads up.
Cheers,
Ian.
prev parent reply other threads:[~2022-03-14 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 8:58 Broken devicetree-rebasing history Hector Martin
2022-03-11 9:01 ` Ian Campbell
2022-03-13 12:00 ` Ian Campbell
2022-03-14 20:38 ` Ian Campbell [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=5406cf9c36cde3bc090365f96e5fdfde017af643.camel@hellion.org.uk \
--to=ijc@hellion.org.uk \
--cc=devicetree@vger.kernel.org \
--cc=j@jannau.net \
--cc=marcan@marcan.st \
--cc=mark.kettenis@xs4all.nl \
--cc=robh+dt@kernel.org \
--cc=sven@svenpeter.dev \
/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).