public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 0ac1ed294cab836e10f3f80f2d57d0e868a198a1
Date: Sat, 24 Aug 2013 18:39:06 +0200	[thread overview]
Message-ID: <20130824163906.93FA720542@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, next has been updated
       via  0ac1ed294cab836e10f3f80f2d57d0e868a198a1 (commit)
      from  dea399178ec1cb67d8235cc476a82dcd6a24080c (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 0ac1ed294cab836e10f3f80f2d57d0e868a198a1
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Sat Aug 24 18:38:34 2013 +0200

    tor: bump package version nr.

-----------------------------------------------------------------------

Summary of changes:
 lfs/tor | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Difference in files:
diff --git a/lfs/tor b/lfs/tor
index ae63d96..6161a56 100644
--- a/lfs/tor
+++ b/lfs/tor
@@ -32,7 +32,7 @@ DL_FROM    = $(URL_IPFIRE)
 DIR_APP    = $(DIR_SRC)/$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
 PROG       = tor
-PAK_VER    = 2
+PAK_VER    = 3
 
 DEPS       = "libevent2"
 


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2013-08-24 16:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20130824163906.93FA720542@argus.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@lists.ipfire.org \
    /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