| To: | Nathan Scott <nathans@xxxxxxxxxx> |
|---|---|
| Subject: | Re: pcp updates: new pcp-atop implementation |
| From: | fche@xxxxxxxxxx (Frank Ch. Eigler) |
| Date: | Wed, 27 May 2015 14:58:24 -0400 |
| Cc: | pcp <pcp@xxxxxxxxxxx>, Stan Cox <scox@xxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <1044667991.6256856.1432708241762.JavaMail.zimbra@xxxxxxxxxx> (Nathan Scott's message of "Wed, 27 May 2015 02:30:41 -0400 (EDT)") |
| References: | <32035133.6250974.1432707468770.JavaMail.zimbra@xxxxxxxxxx> <1044667991.6256856.1432708241762.JavaMail.zimbra@xxxxxxxxxx> |
| User-agent: | Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) |
Nathan Scott <nathans@xxxxxxxxxx> writes: > [...] > src/pcp/atop/atop.1 | 3856 > ++++++++++++++++++------------------- > src/pcp/atop/atop.c | 1718 +++++++++++++--- > [...] OK, that answers my question about how this code is to be shipped. Could you explain the motivation for forking atop (as contrasted with adding PMAPI extensions into upstream atop)? Separately, does this imply a pcp policy change that bundling third-party sources into the main pcp repo is henceforth considered acceptable? - FChE |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | pcp updates: github issue #11: Use sig_atomic_t within signal handlers, Dave Brolley |
|---|---|
| Next by Date: | [Bug 1225599] default-on for pmcd/etc. under new fedora packaging guidelines, bugzilla |
| Previous by Thread: | pcp updates: new pcp-atop implementation, Nathan Scott |
| Next by Thread: | Re: pcp updates: new pcp-atop implementation, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |