The readme provides a high-level overview of how to upgrade top(1).
MFC after: 1 week
Submitted by: Randy Westlund <rwestlun@gmail.com>
Sponsored by: EMC / Isilon Storage Division
Differential D6493
Add compat/top/FREEBSD-upgrade rwestlun_gmail.com on May 22 2016, 7:50 AM. Authored by Tags None Referenced Files
Subscribers None
Details
The readme provides a high-level overview of how to upgrade top(1). MFC after: 1 week
Diff Detail
Event TimelineComment Actions Update notes with a description of our local changes to top(1), and what it will take to apply it to 3.8-beta1. Comment Actions Update with details about changes that have been made and what still needs resolving. Comment Actions The goal of the FREEBSD-upgrade file is to provide a means for tersely describing where the project came from, and where one can bootstrap source for the next upgrade.
Comment Actions Just to be clear, these directions should *only* refer to what is done for 3.5. In particular, using the example I provided earlier (atf [1]), it only provides high-level directions for how the autoconf stuff was generated. I can obtain a diff between the vendor source and the source in the tree -- why do our modifications need to be itemized in such granular detail? This makes the document more likely become stale in the future. https://svnweb.freebsd.org/base/head/contrib/atf/FREEBSD-upgrade?revision=272056&view=markup
Comment Actions
Comment Actions Ok, much better.. walking through the changes between the vendor tree and ^/head/contrib/top, there are some files that have been renamed:
If you document those -- I'll commit the read me. |