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, thirteen, updated. 5cba361800e14e4d8d698686a2d634126018f646
Date: Sat, 24 Nov 2012 14:23:50 +0100	[thread overview]
Message-ID: <20121124132350.43DA720376@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1315 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, thirteen has been updated
       via  5cba361800e14e4d8d698686a2d634126018f646 (commit)
      from  43f4c938c18775afd3ed03295c1dbdbca588d761 (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 5cba361800e14e4d8d698686a2d634126018f646
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Sat Nov 24 14:23:37 2012 +0100

    cpufrequtils: Bump release version.

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

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

Difference in files:
diff --git a/lfs/cpufrequtils b/lfs/cpufrequtils
index e93a65d..6e38b0a 100644
--- a/lfs/cpufrequtils
+++ b/lfs/cpufrequtils
@@ -33,7 +33,7 @@ DIR_APP    = $(DIR_SRC)/$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
 SUP_ARCH   = i586
 PROG       = cpufrequtils
-PAK_VER    = 5
+PAK_VER    = 6
 
 DEPS       = ""
 


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

                 reply	other threads:[~2012-11-24 13:23 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=20121124132350.43DA720376@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