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. 5a33fd9bc6123e9073ecb0976c72d4be4e4f8b5e
Date: Tue, 22 Mar 2022 07:52:50 +0000	[thread overview]
Message-ID: <4KN3cg1MG0z2xhs@people01.haj.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1506 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  5a33fd9bc6123e9073ecb0976c72d4be4e4f8b5e (commit)
      from  7751dcccdd3db5e3bc119a56f76178f691ea9ac0 (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 5a33fd9bc6123e9073ecb0976c72d4be4e4f8b5e
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date:   Tue Mar 22 07:51:17 2022 +0000

    Nano: Braindead me overlooked the rootfiles were misplaced
    
    This was introduced in b1c25d7a8456b7ff05f23c461c623dc18fddbae4, and
    subsequently broke the nightly builds, and I failed to spot this in the
    first place. :-/
    
    Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>

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

Summary of changes:
 config/rootfiles/{core => common}/nano | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename config/rootfiles/{core => common}/nano (100%)

Difference in files:
diff --git a/config/rootfiles/core/nano b/config/rootfiles/common/nano
similarity index 100%
rename from config/rootfiles/core/nano
rename to config/rootfiles/common/nano


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

                 reply	other threads:[~2022-03-22  7:52 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=4KN3cg1MG0z2xhs@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