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: Sun, 13 Mar 2022 12:00:00 +0000 [thread overview]
Message-ID: <677bf0dcf6b17eb7fb5489524e0c4ac4ad450ff0.camel@hellion.org.uk> (raw)
In-Reply-To: <82ba9727b15e99f47488e3b2db4423a51a05bc35.camel@hellion.org.uk>
On Fri, 2022-03-11 at 09:01 +0000, Ian Campbell wrote:
> Thanks for the heads up, I'll (hopefully) take a look over the
> weekend.
My first attempt at rerunning the conversion still had the problem (I
think I didn't wind the state branch back far enough). A second one is
running now and looks to have avoided the issue. I think it'll finish
later on today but I may not have a chance to check and push the
results until later in the week.
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.
FYI the new mirror will be
https://github.com/ijc/devicetree-rebasing-v3 and the new state repo
will be https://github.com/ijc/devicetree-conversion-state-v3. The old
state repo will remain frozen.
Cheers,
Ian.
next prev parent reply other threads:[~2022-03-13 12:00 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 [this message]
2022-03-14 20:38 ` Ian Campbell
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=677bf0dcf6b17eb7fb5489524e0c4ac4ad450ff0.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).