Jim Gifford wrote these words on 04/29/05 02:11 CST: > Matthew Burgess wrote: >>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. > > 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.
Anarchy reigns. :-) -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] 02:20:59 up 27 days, 1:54, 2 users, load average: 0.34, 0.17, 0.06 -- http://linuxfromscratch.org/mailman/listinfo/lfs-book FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
