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. a26a1e16983dbcfc3dd73ab2cddd1fce69223134
Date: Thu, 11 Jun 2015 14:30:50 +0200	[thread overview]
Message-ID: <20150611123050.A3C4E21E9E@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1293 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  a26a1e16983dbcfc3dd73ab2cddd1fce69223134 (commit)
       via  e36af11945c8217a2bc957e42aa87c6578ab573e (commit)
      from  36215f793fd455c1721844ee95a535b19636d1d5 (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 a26a1e16983dbcfc3dd73ab2cddd1fce69223134
Merge: e36af11 36215f7
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Thu Jun 11 14:30:44 2015 +0200

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

commit e36af11945c8217a2bc957e42aa87c6578ab573e
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Wed Jun 10 21:12:04 2015 +0200

    paks: Remove unintentional tab
    
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

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

Summary of changes:

Difference in files:


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

                 reply	other threads:[~2015-06-11 12:30 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=20150611123050.A3C4E21E9E@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