Community
Participate
Working Groups
Bug: each entry in an incoming CONF_SLAVES_INFO packet is being logged as a distinct packet. Improvement: dump the contents of an incoming CONF_SLAVES_INFO. I.e., show what slaves are being reported to us.
Created attachment 173053 [details] fix
Committed. Thanks!
Eugene, I think the iplog flag is to identify contributions that are not from Eclipse committers. A patch from a committer in another project is considered equally "clean", I believe. I'm a committer on the CDT project.
(In reply to comment #3) > Eugene, I think the iplog flag is to identify contributions that are not from > Eclipse committers. A patch from a committer in another project is considered > equally "clean", I believe. I'm a committer on the CDT project. OK
(In reply to comment #3) > Eugene, I think the iplog flag is to identify contributions that are not from > Eclipse committers. A patch from a committer in another project is considered > equally "clean", I believe. I'm a committer on the CDT project. Nope, all contributions from non-committers to the given project need to be noted in the project's IP log. If a project has multiple components with separate commit rights for each component (like platform) then you don't need to enter the contribution in the log.
(In reply to comment #5) > Nope, all contributions from non-committers to the given project need to be > noted in the project's IP log. If a project has multiple components with > separate commit rights for each component (like platform) then you don't need > to enter the contribution in the log. That doesn't make sense to me, as all committers are bound by the same set of rules regarding IP, but certainly not worth further discussion. I'll revert the ipflag.
Moving bugs to new home for IP log.
Bulk change: Marking all bugs from the TM era (until June 2011) target 0.3