Matthew Burgess wrote:
Randy McMurchy wrote:
It would be nice for folks like me that are following these updates to actually have something worthwhile in the log:
Indeed, and if you can't describe the changes in one sentence, it suggests that commit was changing unrelated things. Remember guys, it's nice if we could stick to a "one commit per distinct change" approach - just to make reviewing/commenting/understanding easier.
Cheers,
Matt.
Right now we are just trying to get the build issues worked out, some of the changes we are making affect more than one section. This is an totally unstable branch, I don't see the reason to follow the normal guidelines, until it's stable. Once it's stable then yes, one commit per change is the way to go.
-- ------ [EMAIL PROTECTED] [EMAIL PROTECTED]
LFS User # 2577 Registered Linux User # 299986
-- http://linuxfromscratch.org/mailman/listinfo/lfs-book FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
