public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. ca9b4dec63414f158772559afce7f2f520627d29
Date: Fri, 12 May 2023 14:47:52 +0000	[thread overview]
Message-ID: <4QHs7X6M2Jz2xN5@people01.haj.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1237 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  ca9b4dec63414f158772559afce7f2f520627d29 (commit)
      from  3737b8e98edcc536c6071a5bdb8de7fe7277984c (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 ca9b4dec63414f158772559afce7f2f520627d29
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date:   Fri May 12 14:47:28 2023 +0000

    Zut alors, archive.files needs to be executable
    
    Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>

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

Summary of changes:
 src/scripts/archive.files | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 mode change 100644 => 100755 src/scripts/archive.files

Difference in files:
diff --git a/src/scripts/archive.files b/src/scripts/archive.files
old mode 100644
new mode 100755


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

                 reply	other threads:[~2023-05-12 14:47 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=4QHs7X6M2Jz2xN5@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