public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "David Seifert" <soap@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/nethogs/
Date: Sun, 26 Nov 2017 23:11:26 +0000 (UTC)	[thread overview]
Message-ID: <1511737806.6fecdec4263a91a3c954087671aa2063604b81c1.soap@gentoo> (raw)

commit:     6fecdec4263a91a3c954087671aa2063604b81c1
Author:     David Seifert <soap <AT> gentoo <DOT> org>
AuthorDate: Sun Nov 26 12:38:37 2017 +0000
Commit:     David Seifert <soap <AT> gentoo <DOT> org>
CommitDate: Sun Nov 26 23:10:06 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6fecdec4

net-analyzer/nethogs: [QA] Consistent whitespace in metadata.xml

 net-analyzer/nethogs/metadata.xml | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/net-analyzer/nethogs/metadata.xml b/net-analyzer/nethogs/metadata.xml
index 1b55544df34..03dae9d25e4 100644
--- a/net-analyzer/nethogs/metadata.xml
+++ b/net-analyzer/nethogs/metadata.xml
@@ -1,4 +1,4 @@
-<?xml version='1.0' encoding='UTF-8'?>
+<?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
 <pkgmetadata>
 	<maintainer type="project">
@@ -6,12 +6,12 @@
 		<name>Gentoo network monitoring and analysis project</name>
 	</maintainer>
 	<longdescription>
-NetHogs is a small 'net top' tool. Instead of breaking the traffic down
- per protocol or per subnet, like most tools do, it groups bandwidth by 
-process. NetHogs does not rely on a special kernel module to be loaded. 
-If there's suddenly a lot of network traffic, you can fire up NetHogs and 
-immediately see which PID is causing this. This makes it easy to indentify 
-programs that have gone wild and are suddenly taking up your bandwidth.
+		NetHogs is a small 'net top' tool. Instead of breaking the traffic down
+		per protocol or per subnet, like most tools do, it groups bandwidth by
+		process. NetHogs does not rely on a special kernel module to be loaded.
+		If there's suddenly a lot of network traffic, you can fire up NetHogs and
+		immediately see which PID is causing this. This makes it easy to indentify
+		programs that have gone wild and are suddenly taking up your bandwidth.
 	</longdescription>
 	<upstream>
 		<remote-id type="sourceforge">nethogs</remote-id>


             reply	other threads:[~2017-11-26 23:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-26 23:11 David Seifert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-08 18:54 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/nethogs/ Arthur Zamarin
2025-03-08 15:33 Sam James
2025-01-25 17:03 Sam James
2023-04-25 20:57 Sam James
2022-12-16  7:51 Sam James
2022-12-16  7:51 Sam James
2022-04-05  1:11 Sam James
2021-03-15 23:30 Sam James
2021-03-15 23:30 Sam James
2021-03-15 23:30 Sam James
2021-01-05 20:51 Sam James
2020-12-29 17:14 Sam James
2020-08-20  7:31 Jeroen Roovers
2019-08-22 15:13 Jeroen Roovers
2018-09-20 15:20 Jeroen Roovers
2017-03-28 12:05 Lars Wendler
2017-01-15  8:02 Justin Lecher
2016-12-24 10:18 Agostino Sarubbo
2016-12-24  9:47 Agostino Sarubbo
2016-01-15  6:18 Jeroen Roovers
2015-08-21  8:34 Justin Lecher

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=1511737806.6fecdec4263a91a3c954087671aa2063604b81c1.soap@gentoo \
    --to=soap@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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