Bit tardy, apologies ..
> -----Original Message-----
> From: pcp-bounces@xxxxxxxxxxx [mailto:pcp-bounces@xxxxxxxxxxx] On Behalf
> Of Mark Goodwin
> Sent: Monday, 25 May 2015 2:03 PM
> To: pcp
> Subject: [pcp] pcp updates: merge kenj (pmlogextract, various data type
fixes
> and logrewrite, linux_proc fixes, debian packaging issue, pmdaproc) +
Lukas
> (qa, fedora spec) + nathans (pmdalinux fixes, pmdaproc, qa, build fixes) +
> Martins (types in linux_proc)
>
> Anyone know who the " EC2 Default User" user is? They submitted a valgrind
> inspired memleak fix - the authorship might need fixing up.
Perhaps we need a discussion about our maintainer workflow for pull requests
from github.
Since I don't want to review, build, test, refine a pull request from github
in a github tree, I chose the following workflow in my git tree based on
the pcp.io repository ...
- in this instance
$ git remote add marc https://github.com/marcliangma7/pcp.git
but the <name> (marc) and the <url> might be different
- $ git fetch marc
- $ tig remotes/marc/fix-memory-leak-in-libpcp-pmda
- cherry pick the commit(s) in question
- review, build, test, ...
- push back to pcp.io in my git tree
- wait for review and pulling into the official tree
If there is a better workflow, I'm all ears.
I have no clue if the "EC2 Default User" is specific to the way
"marcliangma" committed on github or is generic to any commit made directly
on github.
|