public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. fbbf44c62f509cdcc2e97e624137e6e64ad33dd9
Date: Fri, 05 Feb 2021 17:14:14 +0000	[thread overview]
Message-ID: <4DXMTf4dXKz2xcJ@people01.haj.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1359 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, master has been updated
       via  fbbf44c62f509cdcc2e97e624137e6e64ad33dd9 (commit)
      from  c1b356d20da2ebb162072787927b5babbafebfa4 (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 fbbf44c62f509cdcc2e97e624137e6e64ad33dd9
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Fri Feb 5 17:13:56 2021 +0000

    fireperf: I accidentially committed an empty rootfile
    
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

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

Summary of changes:
 config/rootfiles/packages/fireperf | 1 +
 1 file changed, 1 insertion(+)

Difference in files:
diff --git a/config/rootfiles/packages/fireperf b/config/rootfiles/packages/fireperf
index e69de29bb..bf6e51e71 100644
--- a/config/rootfiles/packages/fireperf
+++ b/config/rootfiles/packages/fireperf
@@ -0,0 +1 @@
+usr/bin/fireperf


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

                 reply	other threads:[~2021-02-05 17: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=4DXMTf4dXKz2xcJ@people01.haj.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