Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Raúl Sánchez Siles" <rasasi78@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/1] Allow svn tags and branches notation in $(PKG)_VERSION variable.
Date: Thu, 19 Sep 2013 23:58:55 +0200	[thread overview]
Message-ID: <2873382.jskDvbugG2@portaka> (raw)
In-Reply-To: <87fvt0fwix.fsf@dell.be.48ers.dk>

Hi:

  Even that I understand Tom's answer as a NAK, I decided to send a revision 
of the previous patch, just for the record. In this version the last modified 
svn revision for the tag (or branch) is retrieved (and exactly that).

  Maybe someone can come with better and acceptable ideas from the buildroot 
point of view.

  I still consider the key point is being able to encode the revision into the 
$(PKG)_SOURCE variable.

  Regards,

Ra?l S?nchez Siles (1):
  Allow svn tags and branches notation in $(PKG)_VERSION variable.

 docs/manual/adding-packages-generic.txt | 2 ++
 package/pkg-download.mk                 | 4 +++-
 2 files changed, 5 insertions(+), 1 deletion(-)

-- 
1.8.4.rc3
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130919/05db55a5/attachment.asc>

  parent reply	other threads:[~2013-09-19 21:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18  5:11 [Buildroot] [PATCH 1/1] Allow svn tags and branches notation in $(PKG)_VERSION variable Raúl Sánchez Siles
2013-09-18 17:20 ` Thomas Petazzoni
2013-09-19 19:20   ` Peter Korsgaard
2013-09-19 21:54     ` [Buildroot] [PATCH v2 " Raúl Sánchez Siles
2013-09-19 21:58     ` Raúl Sánchez Siles [this message]
2013-09-19 22:04       ` [Buildroot] [PATCH v2 0/1] " Raúl Sánchez Siles
2013-09-20  4:28       ` 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=2873382.jskDvbugG2@portaka \
    --to=rasasi78@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox