On Thu, Apr 2, 2015, at 08:22 PM, Philip Guenther wrote: > On Thu, Apr 2, 2015 at 11:15 AM, Philip Guenther <[email protected]> > wrote: > > On Thu, Apr 2, 2015 at 10:48 AM, Adam Wolk <[email protected]> wrote: > > ... > >> My questions is how valuable are dmesgs from snapshots & past releases? > >> - Should I care to email the dmesg from the 5.6 installation when 5.7 > >> is almost shipped? > >> - Is it valuable for the project to upgrade to 5.7 just for the dmesg > >> even if I intend to run > >> current snapshots? > >> - In case I'm going to only run snapshots - should I send a dmesg from > >> the first snapshot > >> installed on that box? > > > > > > Send the dmesg from the version you run. > > If something changes after an upgrade, or just every few upgrades, > > send a new dmesg. > > To continue: > > As developers, we look at the submitted dmesgs to see which devices > are still in use (or not!), what new stuff is appearing, what stuff > has changed, etc. But we're mostly interested in the present; sending > both a 5.6 and 5.7 dmesg is only useful if something broke between the > two, but if that's the case you should post it to the mailing lists as > dmesg@ is just dropped into a file and only (re)viewed > retrospectively. > > > Philip Guenther
Thanks Philip. In that case I'll go with the B path as I have a 5.6 CD handy so won't have to prep a snapshot media and just upgrade with a bsd.rd. I'll provide a 5.6 dmesg & will send a snapshot dmesg if anything changes for better or worse with the snapshot. Regards, Adam
