Hi all, Sorry to be a stick-in-the-mud, and perhaps it's just me, but I don't like this "lump everything in one ticket" idea (using the BLFS-6.2.0 Text Changes ticket as an example). I find it difficult (if not impossible) to figure out:
1. What has been taken care of? 2. What is still under discussion? 3. Who is working on what? 4. What is still open? I'd prefer if we go back to the tried-and-true method of opening a ticket when there's an issue, and closing it when it is fixed. Perhaps I'm just old-fashioned. -- Randy rmlscsi: [bogomips 1003.26] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3] [GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686] 00:39:00 up 35 days, 53 min, 1 user, load average: 0.05, 0.25, 0.52 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
