All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1 v2] libvpx: bump version to 1.4.0
Date: Thu, 9 Apr 2015 07:43:39 +0300	[thread overview]
Message-ID: <20150409044339.GH2241@tarshish> (raw)
In-Reply-To: <5525AF73.2080101@proximus.be>

Hi Johan,

On Thu, Apr 09, 2015 at 12:45:07AM +0200, Johan Sagaert wrote:
> Thomas Petazzoni schreef op 8/04/2015 om 22:51:
> >On Wed,  8 Apr 2015 00:53:31 +0200, Sagaert Johan wrote:
> >>Use tar.bz2 instead of git.
> >>Also added the hash file.
> >>Changes: https://chromium.googlesource.com/webm/libvpx/+/0080aca235e2d677e49ff46c3e8e77d9dd15858c/CHANGELOG
> >>
> >>Signed-off-by: Sagaert Johan <sagaert.johan@proximus.be>
> >Thanks, applied, after removing the unnecessary LIBVPX_VERSION_MAJOR
> >variable, as suggested by Arnout.
>
> Fine, thanks :
> Is there a thumb rule  when this is needed  ?  I see many packages use this
> scheme .

We split the _MAJOR part of the version when it is used on its one, e.g. for 
_SITE name.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

      reply	other threads:[~2015-04-09  4:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 22:53 [Buildroot] [PATCH 1/1 v2] libvpx: bump version to 1.4.0 Sagaert Johan
2015-04-08 20:11 ` Arnout Vandecappelle
2015-04-08 20:51 ` Thomas Petazzoni
2015-04-08 22:45   ` Johan Sagaert
2015-04-09  4:43     ` Baruch Siach [this message]

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=20150409044339.GH2241@tarshish \
    --to=baruch@tkos.co.il \
    --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.