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. d0552ea9bfc1dc55fc5930128b60877fad4da444
Date: Thu, 09 Apr 2015 15:36:59 +0200	[thread overview]
Message-ID: <20150409133659.A2D8A21ACE@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1219 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  d0552ea9bfc1dc55fc5930128b60877fad4da444 (commit)
       via  80d83d13d8a1e794e7e4d1da90f83f297ce04191 (commit)
      from  ad592fb878653d2abf970da02453d4a4893ac0a9 (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 d0552ea9bfc1dc55fc5930128b60877fad4da444
Merge: 80d83d1 ad592fb
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Thu Apr 9 15:36:45 2015 +0200

    Merge branch 'next' of ssh://git.ipfire.org/pub/git/ipfire-2.x into next

commit 80d83d13d8a1e794e7e4d1da90f83f297ce04191
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Thu Apr 9 15:36:27 2015 +0200

    strongswan: Rootfile update

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

Summary of changes:

Difference in files:


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

                 reply	other threads:[~2015-04-09 13:36 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=20150409133659.A2D8A21ACE@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