Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


Hi :)
A dev might have more joy with the very functional GMane interface rather than the gui prettiness 
of Nabble.

Even so i think this list is too high-volume to be data-mined for the required information and 
anyway it's extremely rare that specific bug reports are referenced either by name (however vague 
and inaccurate) or number.  

Where threads do mention bug-report numbers it's done in a very inconsistent way, sometimes as part 
of a url sometimes with or without a # (as in bug #blah) and sometimes just the number so you would 
have had to be following the thread to realise it was a bug-report number.  

That might all sound very negative but this list is mainly trying to solve problems partly to avoid 
people having to post bug-reports.  Often answers here will be work-arounds or explain quirks or 
why things work slightly differently in LO than other products a new users might have used 
previously.  It's very rare that people ask a question here that results in a bug-report getting 
posted and even then it's usually a feature request or wish-list item.  


So, although i think your idea to try to do a bit of data-mining is good i think it's impractical 
for this list and that Michael Meeks handled it best by just asking for people to list specific 
examples.  

Good luck all and much appreciated
Regards from
Tom :)  


--- On Fri, 17/8/12, V Stuart Foote <VStuart.Foote@utsa.edu> wrote:

From: V Stuart Foote <VStuart.Foote@utsa.edu>
Subject: RE: [libreoffice-users] Re: Excuse me, but your opinion is simplyunimportant. Start over 
and you can expect more of the same.
To: michael.meeks@suse.com, users@global.libreoffice.org
Date: Friday, 17 August, 2012, 2:05

Michael,
 
It is pretty rare for specifics of bugs to be entered on the Users list, where there might have a 
passing comment that a bug would be or had been filed. But often no additional details of the bug 
in the discussion. But, that said, the threads are pretty descriptive.
 
Being a new subscriber, maybe the Nabble web interface would be of use to efficiently identify 
substantive issues that may have associated bugs.
 
http://nabble.documentfoundation.org/Users-f1639498.html
 
Stuart
 

________________________________

From: Michael Meeks [mailto:michael.meeks@suse.com]
Sent: Thu 8/16/2012 11:50 AM

<snip>
        One thing that frustrates me, since I've only just subscribed is that
we seem to be talking about a load of bugs with no numbers I can easily
lookup.

        I'd greatly appreciate it if some kind soul could scrape the thread in
their mailbox for a list of bug links to the most significant issues and
aggregate them in a single mail - so I can go and triage them.
<snip>
 

-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted


-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.