On Tue, Jun 25, 2019 at 02:36:30PM +0200, Olof Johansson wrote: > On Tue, Jun 25, 2019 at 2:32 PM Maxime Ripard 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. Ok, so you'd prefer something like , -2 if there's multiple, subsequent, PR, and , -again if the latter replaces the former? Maxime -- Maxime Ripard, Bootlin Embedded Linux and Kernel engineering https://bootlin.com