Which is perfectly acceptable IMHO. There is no reason that a cset need
document all the details when the file logs already do. A cset need only
indicate what basic work is being done and maybe a list of files in the
cset. Doing a bk changes -v gets the file comments as well for those
people that want them.
I actually like the individual file comments part of the cset setup. It's
what my preferred use is when I'm making my own patches. Make the cset
have a summary of the major changes, then let each file have it's own
detail change information.
-- Doug Ledford <dledford@redhat.com> 919-754-3700 x44233 Red Hat, Inc. 1801 Varsity Dr. Raleigh, NC 27606 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/