From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 9aefd1ed07eee7d83e5b274d4a83240811f9e091
Date: Tue, 03 Jul 2018 20:04:36 +0100 [thread overview]
Message-ID: <20180703190436.D3F491081BA5@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1490 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 9aefd1ed07eee7d83e5b274d4a83240811f9e091 (commit)
from 716c4751e71f63f923a3cb0ed32ad17b4fbdb1d0 (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 9aefd1ed07eee7d83e5b274d4a83240811f9e091
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Tue Jul 3 20:01:46 2018 +0100
usbutils: Update rootfile
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/usbutils | 1 -
1 file changed, 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/common/usbutils b/config/rootfiles/common/usbutils
index 1162c3ab1..f0bdc522b 100644
--- a/config/rootfiles/common/usbutils
+++ b/config/rootfiles/common/usbutils
@@ -2,7 +2,6 @@ usr/bin/lsusb
usr/bin/lsusb.py
usr/bin/usb-devices
usr/bin/usbhid-dump
-usr/sbin/update-usbids.sh
#usr/share/hwdata
#usr/share/hwdata/usb.ids
#usr/share/man/man1/usb-devices.1
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-07-03 19:04 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=20180703190436.D3F491081BA5@git01.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