Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/snappy: bump version
Date: Sun, 2 Oct 2016 21:44:30 +0200	[thread overview]
Message-ID: <20161002194430.GA4066@free.fr> (raw)
In-Reply-To: <87eg3ypmy6.fsf@dell.be.48ers.dk>

Peter, All,

On 2016-10-02 21:31 +0200, Peter Korsgaard spake thusly:
> >>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
>  > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> 
> For these bump-to-another-git-revision changes I would prefer some
> context / details. For bumps to a new release we at least know that the
> maintainer thinks the sw is ready to be used. With random git versions
> not so much.
> 
> E.G. has some important bugfix or new feature been added? Have you used
> it yourself? Is the new hash the latest commit in the repo or something
> else? ..

Here's your commit log:

There's been a single release of snappy since the move from GoogleCode
to Github; that release was more than a year ago. In that time frame,
only 14 commits went in master, of which to merges, so about 1 real
commit per month...

For a brief summary of additional stuff since the last release:
  - provide snappy.pc
  - a few generic bug fixes, as well as a few ARM-specific ones
  - a few buildsystem fixes

Since we can't say releases are made on a timely cadence, let's just hop
to the latest master from the git tree.

;-)

> Anyway - Committed, thanks.

Thanks!

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2016-10-02 19:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-01 19:04 [Buildroot] [PATCH 1/2] package.snappy: fix static builds Yann E. MORIN
2016-10-01 19:04 ` [Buildroot] [PATCH 2/2] package/snappy: bump version Yann E. MORIN
2016-10-02 19:31   ` Peter Korsgaard
2016-10-02 19:44     ` Yann E. MORIN [this message]
2016-10-02 19:52       ` Peter Korsgaard
2016-10-02 19:19 ` [Buildroot] [PATCH 1/2] package.snappy: fix static builds 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=20161002194430.GA4066@free.fr \
    --to=yann.morin.1998@free.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox