From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, thirteen, updated. e1f3cb88a8adc5ee004fb54982c06193374e7102
Date: Thu, 22 Nov 2012 20:48:31 +0100 [thread overview]
Message-ID: <20121122194832.01E132039E@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1380 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, thirteen has been updated
via e1f3cb88a8adc5ee004fb54982c06193374e7102 (commit)
from b9d4e380c7099f67f32b030ac78bc02acd58ca7f (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 e1f3cb88a8adc5ee004fb54982c06193374e7102
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Nov 22 20:47:59 2012 +0100
ncurses: Add tset (reset links to tset).
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/ncurses | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/common/ncurses b/config/rootfiles/common/ncurses
index dbb30aa..46b3bd9 100644
--- a/config/rootfiles/common/ncurses
+++ b/config/rootfiles/common/ncurses
@@ -9,7 +9,7 @@ usr/bin/reset
#usr/bin/tic
#usr/bin/toe
usr/bin/tput
-#usr/bin/tset
+usr/bin/tset
#usr/include/curses.h
#usr/include/cursesapp.h
#usr/include/cursesf.h
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2012-11-22 19:48 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=20121122194832.01E132039E@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