public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 9be5274ac44654acfa0e27220221997955420013
Date: Fri, 27 Apr 2012 14:14:25 +0200	[thread overview]
Message-ID: <20120427121425.CBE2C20188@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1500 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 3.x development tree".

The branch, master has been updated
       via  9be5274ac44654acfa0e27220221997955420013 (commit)
      from  9a1db8ec4ee4ede35348104ab72459011d6cee33 (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 9be5274ac44654acfa0e27220221997955420013
Author: Christian Schmidt <christian.schmidt(a)ipfire.org>
Date:   Fri Apr 27 14:08:43 2012 +0200

    samba: Update to version 3.6.4.
    
    Fixes #10082, CVE-2012-1182

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

Summary of changes:
 samba/samba.nm |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

Difference in files:
diff --git a/samba/samba.nm b/samba/samba.nm
index 5902b9b..6403e4c 100644
--- a/samba/samba.nm
+++ b/samba/samba.nm
@@ -4,8 +4,8 @@
 ###############################################################################
 
 name       = samba
-version    = 3.6.3
-release    = 2
+version    = 3.6.4
+release    = 1
 
 maintainer = Christian Schmidt <christian.schmidt(a)ipfire.org>
 groups     = Networking/Daemons


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

                 reply	other threads:[~2012-04-27 12:14 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=20120427121425.CBE2C20188@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