From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] python-pip: bump to version 19.0.3
Date: Fri, 22 Feb 2019 22:34:28 +0100 [thread overview]
Message-ID: <20190222223428.232c9a46@windsurf> (raw)
In-Reply-To: <20190222085324.7343-2-asafka7@gmail.com>
Hello Asaf,
On Fri, 22 Feb 2019 10:53:21 +0200
Asaf Kahlon <asafka7@gmail.com> wrote:
> Signed-off-by: Asaf Kahlon <asafka7@gmail.com>
> ---
> package/python-pip/python-pip.hash | 4 ++--
> package/python-pip/python-pip.mk | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
This patch did not apply to our next branch, because the next branch
already had python-pip 19.0.2 and not 19.0.1. I fixed things up
manually, but when there is a "next" branch opened (which is the case
between -rc1 and the final release), your version bump patches should
be based on the next branch, not on master.
Also, please use "package/foo:" as the prefix for the commit title.
Applied to next, thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-02-22 21:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 8:53 [Buildroot] [PATCH 1/1] czmq: bump to version 4.2.0 Asaf Kahlon
2019-02-22 8:53 ` [Buildroot] [PATCH 1/1] python-pip: bump to version 19.0.3 Asaf Kahlon
2019-02-22 21:34 ` Thomas Petazzoni [this message]
2019-02-22 8:53 ` [Buildroot] [PATCH 1/1] python-psutil: bump to version 5.5.1 Asaf Kahlon
2019-02-23 13:29 ` Thomas Petazzoni
2019-02-22 8:53 ` [Buildroot] [PATCH 1/1] python-py: bump to version 1.8.0 Asaf Kahlon
2019-02-23 13:29 ` Thomas Petazzoni
2019-02-22 8:53 ` [Buildroot] [PATCH 1/1] python-pyzmq: bump to version 18.0.0 Asaf Kahlon
2019-02-23 13:31 ` Thomas Petazzoni
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=20190222223428.232c9a46@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.