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. b1c25d7a8456b7ff05f23c461c623dc18fddbae4
Date: Mon, 21 Mar 2022 19:02:18 +0000	[thread overview]
Message-ID: <4KMkWZ2zmhz2xlT@people01.haj.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2135 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  b1c25d7a8456b7ff05f23c461c623dc18fddbae4 (commit)
      from  e6cbe7563f1e9e92b77c4d30aa76cbac27d71103 (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 b1c25d7a8456b7ff05f23c461c623dc18fddbae4
Author: Jon Murphy <jon.murphy(a)ipfire.org>
Date:   Thu Mar 17 12:06:29 2022 -0500

    Nano: Move nano editor from packages to core system
    
    - this will not change the default editor `vim`
    
    Signed-off-by: Jon Murphy <jon.murphy(a)ipfire.org>
    Acked-by: Peter Müller <peter.mueller(a)ipfire.org>
    Acked-by: Michael Tremer <michael.tremer(a)ipfire.org>

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

Summary of changes:
 config/rootfiles/{packages => core}/nano | 0
 lfs/nano                                 | 7 -------
 2 files changed, 7 deletions(-)
 rename config/rootfiles/{packages => core}/nano (100%)

Difference in files:
diff --git a/config/rootfiles/packages/nano b/config/rootfiles/core/nano
similarity index 100%
rename from config/rootfiles/packages/nano
rename to config/rootfiles/core/nano
diff --git a/lfs/nano b/lfs/nano
index df994364f..f82e8d4f9 100644
--- a/lfs/nano
+++ b/lfs/nano
@@ -25,19 +25,12 @@
 include Config
 
 VER        = 6.1
-SUMMARY    = Pico editor clone with enhancements
 
 THISAPP    = nano-$(VER)
 DL_FILE    = $(THISAPP).tar.xz
 DL_FROM    = $(URL_IPFIRE)
 DIR_APP    = $(DIR_SRC)/$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
-PROG       = nano
-PAK_VER    = 41
-
-DEPS       = ""
-
-SERVICES   =
 
 ###############################################################################
 # Top-level Rules


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

                 reply	other threads:[~2022-03-21 19:02 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=4KMkWZ2zmhz2xlT@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