All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 2/2] package/libinput: bump version to 1.18.0
Date: Tue, 27 Jul 2021 22:43:40 +0200	[thread overview]
Message-ID: <20210727224340.0dbaffd6@gmx.net> (raw)
In-Reply-To: <20210724094931.3e30dfeb@windsurf>

Hello Arnout, Thomas,

On Sat, 24 Jul 2021 09:49:31 +0200, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

> On Thu, 22 Jul 2021 23:18:56 +0200
> Arnout Vandecappelle <arnout@mind.be> wrote:
>
> > On 08/06/2021 21:49, Peter Seiderer wrote:
> > > For details see [1].
> > >
> > > [1] https://lists.freedesktop.org/archives/wayland-devel/2021-June/041849.html
> > >
> > > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> >
> >  Why is this bump in two separate patches? If it's because 1.17.3 should be
> > applied to the 2021.05 branch, then it's better to make two distinct patches,
> > one for master that bumps directly to 1.18.0, and another for stable that is
> > marked explicitly as such with --subject-prefix.

Yes, this was the intention of the split..., will mark it more explicitly next
time...

>
> Gah sorry, I'm only seeing this now after having applied the patches.
> Peter also did the same (bump in several steps) libxmlrpc, so I was not
> too concerned about this. Though I agree that your question makes sense.

For libxmlrpc the same applies for the first patch..., the other two where
split because they where tagged with code/stable and code/advanced, was not
sure about the whole/complete bump but did  not find a downside for the
code/advanced one...

Regards,
Peter

>
> Best regards,
>
> Thomas

_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2021-07-27 20:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 19:49 [Buildroot] [PATCH v1 1/2] package/libinput: bump version to 1.17.3 Peter Seiderer
2021-06-08 19:49 ` [Buildroot] [PATCH v1 2/2] package/libinput: bump version to 1.18.0 Peter Seiderer
2021-07-22 21:18   ` Arnout Vandecappelle
2021-07-24  7:49     ` Thomas Petazzoni
2021-07-27 20:43       ` Peter Seiderer [this message]
2021-08-04 20:29         ` Peter Korsgaard
2021-07-24  7:48 ` [Buildroot] [PATCH v1 1/2] package/libinput: bump version to 1.17.3 Thomas Petazzoni
2021-08-04 20:27 ` Peter Korsgaard

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=20210727224340.0dbaffd6@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.