From: Olof Johansson <olof@lixom.net>
To: Maxime Ripard <maxime.ripard@bootlin.com>
Cc: Chen-Yu Tsai <wens@csie.org>,
ARM-SoC Maintainers <arm@kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] Allwinner Device Tree Changes for 5.3
Date: Tue, 25 Jun 2019 14:36:30 +0200 [thread overview]
Message-ID: <CAOesGMhXVnNuEKHPBo6s9GBWrKAiX8zFPSt89cQRYNS711ymvw@mail.gmail.com> (raw)
In-Reply-To: <20190625123219.hwg5vjz3qocxavn5@flea>
On Tue, Jun 25, 2019 at 2:32 PM Maxime Ripard <maxime.ripard@bootlin.com> wrote:
>
> Hi Olof,
>
> On Tue, Jun 25, 2019 at 04:41:19AM -0700, Olof Johansson wrote:
> > On Fri, Jun 21, 2019 at 10:08:08AM +0200, Maxime Ripard wrote:
> > > Hi,
> > >
> > > Please pull the following changes for the next release.
> > >
> > > Thanks!
> > > Maxime
> > >
> > > The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
> > >
> > > Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
> > >
> > > are available in the Git repository at:
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git refs/tags/sunxi-dt-for-5.3-201906210807
> >
> > You know, there's a timestamp in the tag too, no need to encode it in the name.
>
> Yeah, I've switched to some tooling to send them instead of doing them
> manually, and having a timestamp was the easiest solution to avoid a
> collision, but I guess having it down to the minute was a bit
> overkill. Do you have any preference on this?
Main thing for me is that I can't tell from time timestamps if it's a
respin/new version, or a re-stamp, i.e. if it's something I should
care about or not.
I.e. it doesn't carry any useful signal for the consuming side and is
mostly noise.
-Olof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-25 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 8:08 [GIT PULL] Allwinner Device Tree Changes for 5.3 Maxime Ripard
2019-06-25 11:41 ` Olof Johansson
2019-06-25 12:32 ` Maxime Ripard
2019-06-25 12:36 ` Olof Johansson [this message]
2019-06-25 14:55 ` Maxime Ripard
2019-06-27 2:09 ` Olof Johansson
2019-06-27 8:43 ` Maxime Ripard
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=CAOesGMhXVnNuEKHPBo6s9GBWrKAiX8zFPSt89cQRYNS711ymvw@mail.gmail.com \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maxime.ripard@bootlin.com \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).