devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ijc@hellion.org.uk>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, Frank Rowand <frowand.list@gmail.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Andre Przywara <andre.przywara@arm.com>,
	Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: devicetree-rebasing.git updates pausing for a couple of months
Date: Sun, 18 Aug 2019 19:11:57 +0800	[thread overview]
Message-ID: <0403ebf34d5d13c604e7109d8fb3e4bb6ab3c8a2.camel@hellion.org.uk> (raw)
In-Reply-To: <20190709215403.GA26049@bogus>

(replying to the two subthreads in one go)

On Tue, 2019-07-09 at 15:54 -0600, Rob Herring wrote:
> On Fri, Jun 21, 2019 at 01:01:27PM +0100, Ian Campbell wrote:
> > Hi all,
> > 
> > I've no idea if anyone actually uses it any more, but the split out
> > devicetree only git repo [0] is not going to receive any new updates
> > for a little while (likely 1-2 months) while I relocate to another
> > country.
> 
> Can you sync your move to the kernel release schedule? JK

:-)

I'm back online and have pushed the backlog[0] up to v5.3-rc4-dts.

> Seriously, I've been wondering if we could turn this into a Gitlab CI 
> job instead. Then it's not solely up to you to run it.

That would work for the bulk of the work (daily run of git filter-
branch), the only manual bit is merging the tags of each release (so
approx weekly). I currently sign the tags with my own PGP key so isn't
really suitable for pushing to a CI system (I think that's true no
matter which key we are using?)

On Tue, 2019-06-25 at 09:05 +0200, Sascha Hauer wrote:
> On Tue, Jun 25, 2019 at 09:02:40AM +0200, Sascha Hauer wrote:
> > I am still using it for barebox, so I'd appreciate devicetree-rebasing
> > coming back once you are relocated. Anyway, barebox can live without a
> > dts update for a while, so take your time ;)
> 
> BTW thanks for keeping devicetree-rebasing up to date for all the time.
> If the repository is of no personal use for you anymore, we at
> Pengutronix could offer to take over the repository.

Thanks, it's approximately no actual effort so I don't mind to keep
running it for the time being. So far the real actual work has been
hacking on git filter-branch, which has been a 2-3 events per decade
type thing...

Cheers,
Ian.

[0]
v5.2-rc7-dts v5.2-dts v5.3-rc1-dts v5.3-rc2-dts v5.3-rc3-dts v5.3-rc4-dts

      reply	other threads:[~2019-08-18 11:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21 12:01 devicetree-rebasing.git updates pausing for a couple of months Ian Campbell
2019-06-25  7:02 ` Sascha Hauer
2019-06-25  7:05   ` Sascha Hauer
2019-07-09 21:54 ` Rob Herring
2019-08-18 11:11   ` 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=0403ebf34d5d13c604e7109d8fb3e4bb6ab3c8a2.camel@hellion.org.uk \
    --to=ijc@hellion.org.uk \
    --cc=andre.przywara@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    /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).