On Mon, Aug 25, 2014 at 09:47:29AM -0600, Sebastian Kuzminsky wrote: > > How are long branches handled? For example, only about half of the > > commits in joints_axes5 have SOB tags. Would someone have to edit all > > the commits the next time the branch is rebased? Or would it suffice to > > have a SOB tag on the merge commit?
On Mon, Aug 25, 2014 at 11:12:14AM -0500, Chris Radek wrote: > I think having a cutoff date (which is already in the proposal) is > the best way to deal with this. Commits after we decide to do this > must have s-o-b. Commits from before are the same as they ever > were. So specifically we plan to look at the AuthorDate to determine whether the SOB check is appropriate to perform for a given commit. This date is preserved over e.g., rebases so an old branch like ja5 doesn't have to be massaged before it's either rebased again or pushed to master. Jeff ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
