I'm going to do this again but I can't seem to find the query I used
last time (doh!).
Hey Tommy,
On 02/16/2015 10:28 PM, Tommy wrote:
hi guys, sorry of not being much active in the last month but work
issues brought me away from bugzilla (temporarily)
I wonder if Joel is planning to do another run of the NEW bugs ping.
first test in january had very good results.
of the
On 02/09/2015 08:59 AM, Florian Reisinger wrote:
Hi,
I guess I did miss something... I thought, that the projects of DLP are added
as Components of the DLP. The LibreOffice option is so well hidden in the
list of products
+1. I made a redmine issue about this...I really think it's
/buglist.cgi?keywords=NEEDINFOlist_id=521406
Thanks all.
Best,
Joel
On 02/02/2015 06:32 AM, Florian Reisinger wrote:
Description of the keywords ;)
Liebe Grüße / Yours,
Florian Reisinger
Am 02.02.2015 um 15:28 schrieb Joel Madero jmadero@gmail.com:
On 02/02/2015 02:50 AM, Rob Snelders
On 02/02/2015 02:50 AM, Rob Snelders wrote:
Hi,
Also changing the discriptions if possible would be great.
Changing description of what?
Best,
Joel
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change
Top posting just to say thanks!
Best,
Joel
On 01/31/2015 04:28 AM, Robinson Tryon wrote:
On Fri, Jan 30, 2015 at 1:01 AM, Bjoern Michaelsen
bjoern.michael...@canonical.com wrote:
Nope. Bugzilla is Infra. Infra is on Redmine.
Here are the Bugzilla bugs on redmine:
On 01/31/2015 06:12 AM, bfoman wrote:
jmadero wrote
and try to figure out how that
page is generated. I triedcouldn't find it for the life of me :-/
Hi!
It is quite easy - it is implemented as Extension. The page template is
On 01/29/2015 10:56 PM, Cor Nouws wrote:
Hi Joel,
Joel Madero wrote on 30-01-15 00:13:
Would that be good possible?
I agree that it would be good it is possible.
Can I change add a query myself to that page?
So you can clone our instance of bugzilla: git clone
git
On 01/29/2015 04:01 PM, Bjoern Michaelsen wrote:
Hi,
On Thu, Jan 29, 2015 at 03:13:18PM -0800, Joel Madero wrote:
I agree that it would be good it is possible. I highly recommend we
create a new product bugzilla where we can easily track these
enhancement requests...else they are likely
Hi Guys,
On Sun, 25 Jan 2015 13:25:38 +0100, bfoman
bfo.bugm...@spamgourmet.com wrote:
Time to clean the database from FDO leftovers (keywords, unrelated
series,
etc.).
+1. we really need to remove a lot of those useless keywords and add
some that are nore useful.
morevoer I'd
Just poking the list again to point out that we have 130 potential easy
hacks that are awaiting some code pointers to become actual easy hacks.
I think that these would be great to move forward to encourage more new
blood :)
Hey Tommy,
On Tue, 06 Jan 2015 00:06:02 +0100, Joel Madero
jmadero@gmail.com wrote:
Hi All,
Here is the start of a spreadsheet that can track stats for QA pings.
It's not perfect - as it's limited by how bugzilla is limited - but it
gives some insight as to how the pings are working
Top posting - apologies in a rush :)
I did a NEEDINFO ping today and added this message at the very end:
Message generated on: 10/01/2015
Best,
Joel
On 01/10/2015 04:05 PM, Robinson Tryon wrote:
Adding a unique identifier to the comment during a bulk-update is
great. In fact, bulk updates
Done.
Awesome, thanks Moggi.
Best,
Joel
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Hi All,
We have someone who took the time to get a WinDB log for a crash he's
seeing but no one in QA is seeing the same problem. Can someone take the
time to look at the log to see what's going on (or if it's even enough
to move it forward to NEW). I like to try to respond to users who go the
Hi All,
http://vps2.semesterofcode.com/
https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind1412L=vals-socF=S=P=54
We have until January 15th if there is interest to do this. Anyone have
the bandwidth to go through the process and any mentors available to
take on a student or two?
Best,
Joel
Hey All,
On 06.01.2015 23:58, Joel Madero wrote:
Hi All,
So I suppose we'll start chunking into the next set relatively quickly.
I was thinking at the end of January doing anything 22 months or more,
slowly decrease this to 12 months. I don't want to hit all of these at
once
Hi All,
So I suppose we'll start chunking into the next set relatively quickly.
I was thinking at the end of January doing anything 22 months or more,
slowly decrease this to 12 months. I don't want to hit all of these at
once as there are already nearly 1600. So I think slowly going from 22,
20,
Hi All
On Tue, 06 Jan 2015 00:06:02 +0100, Joel Madero
jmadero@gmail.com wrote:
Hi All,
Here is the start of a spreadsheet that can track stats for QA pings.
To add to this:
25/267 of the bugs were subsequently touched after the QA ping this round.
We might want to review those to see
Hi All,
I just found out that this keyword bisected is being used. I'm curious
who is using it and what it is identifying. Also, I'm curious if we
shouldn't move whatever it is being used for to the whiteboard - having
2 bisect things being in whiteboard, and then 1 in keyword seems strange
to
Hi,
Hi,
On Mon, Jan 05, 2015 at 08:23:20AM -0800, Joel Madero wrote:
A couple people have told me they use the keyword to indicate that the
exact (or nearly the exact) commit has been identified.
I use it like that.
I don't think this is on the wiki - I'll try to add it.
If this is true
Hi All,
Here is the start of a spreadsheet that can track stats for QA pings.
It's not perfect - as it's limited by how bugzilla is limited - but it
gives some insight as to how the pings are working out. The spreadsheet
auto updates after 6,000 seconds (figured no need for faster ;) ).
Requests
Top posting again:
The mass ping has been done. If I'm poked once a month as a reminder
I'll do it monthly so that the list is manageable.
here is a link that I believe we can monitor:
Hey Terrence,
On Mon, 2015-01-05 at 10:03 -0800, Joel Madero wrote:
Top posting again:
The mass ping has been done. If I'm poked once a month as a reminder
I'll do it monthly so that the list is manageable.
here is a link that I believe we can monitor:
https://bugs.freedesktop.org
Hey Tommy,
Top posting because this is finally happening. Before running it
officially I'd like to allow people to see the text I'm using and the
query I'm going to use it on.
Text: http://pastebin.com/7GiJnj7N (note, not looking for nit-picky, but
if there is a serious problem with it, please
On 12/30/2014 12:41 PM, Terrence Enger wrote:
On Tue, 2014-12-30 at 09:01 -0800, Joel Madero wrote:
Hey Tommy,
Top posting because this is finally happening. Before running it
officially I'd like to allow people to see the text I'm using and the
query I'm going to use it on.
Text: http
Hi All,
To sum up, enhancements opened by UX members are set as NEW and assigned
to UX-advice so they are not triaged by QA members and don't appear in
the QA stats.
By assign - if you set the component to ux-advise then it'll auto
assign it to the UX team and they can tackle it from there.
On 12/17/2014 09:04 AM, Alexander Thurgood wrote:
Le 16/12/2014 13:40, Tommy a écrit :
of the original 83 mab4.2 that were open at the time of 4.2.x EOL, 12
turned to be RESOLVED WORKSFORME in the 4.3.x or 4.4.x branch.
More of interest to me would be to know how many of the moved MABs are
Hi All,
Can someone please test this last 4.2 MAB - it requires Windows and any
RTL language apparently.
https://bugs.freedesktop.org/show_bug.cgi?id=59613
Thanks!
Best,
Joel
___
List Name: Libreoffice-qa mailing list
Mail address:
Hey Tommy,
Any FDO cleanup - if you cc me on it I'll address the issue. Only a few
people have rights as of now.
I see that somebody did the clean up but forgot to remove just the
4.1.6.1 rc
Resolved :) Thanks!
Best,
Joel
___
List Name:
Markus may have something that could work. Going to cc him as he has
thousands of documents for testing purposes.
Best,
Joel
P.S. If not - you could just scrap the FDO site for attachments ;) All
of that is public.
On 12/03/2014 10:06 AM, Lee Fisher wrote:
Hi,
First post. :-)
I'm writing
Hi All,
In order to increase confidence in our bug tracking system, it'd be
great if we could start prioritizing NEW (and other) bugs correctly -
starting with those that are WAY over-prioritized.
Guidance:
https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg
Hey Tommy,
this has been discussed in the last weeks in the QA list and in last
QA call
I'm just curious to know if that test is going to be performed soon.
Sorry I'm incredibly busy - it'll likely be in 2 weeks or so. Before
running it I really want to look at the list and make sure that the
On 11/23/2014 09:21 AM, V Stuart Foote wrote:
@Lera, *,
First thank you for taking on the translation tasks, we know it can be
challenging.
Lera Goncharuk wrote
Do I understand correctly, that we should consult with developers when a
bug
violates principles of mathematical calculations
Hi All,
Well thanks to some amazing work by multiple new and old faces - our bug
count has reached record lows :) To simplify things, Beluga went ahead
and made some cool grouping (no clue howbut it's cool none the less)
that might help experienced developers and QA members target the harder
Hi All,
This set of bugs would be probably most manageable by developers
Compiling/unit tests:
Bug 83241 https://bugs.freedesktop.org/show_bug.cgi?id=83241 - Failing
unit test sw_ooxmlimport building master on OSX 10.9.4 / Xcode 5.1.1
Bug 82694 https://bugs.freedesktop.org/show_bug.cgi?id=82694
Hi All,
Well thanks to some amazing work by multiple new and old faces - our bug
count has reached record lows :) To simplify things, Beluga went ahead
and made some cool grouping (no clue howbut it's cool none the less)
that might help experienced developers and QA members target the harder
On 11/17/2014 04:21 AM, Tommy wrote:
hi there,
according to the release plan the 4.2.x EOL will be november 19th
https://wiki.documentfoundation.org/ReleasePlan#4.2_release
after that day I'll start migrating all the still existing mab4.2 bugs
to the mab4.3 list
however it's not clear to
On 11/17/2014 06:23 AM, Tommy wrote:
On Mon, 17 Nov 2014 15:12:25 +0100, Joel Madero
jmadero@gmail.com wrote:
On 11/17/2014 04:21 AM, Tommy wrote:
.
however it's not clear to me if an extra 4.2.8 release is under
consideration because of the infamous sorting calc bug
4.2.8
Hi All,
A *huge* thank you for all of your tremendous efforts in managing the
chaos which is FDO :) Due to all of your great work we have hit a new
milestone._*599*_! We're under 600 for the first time in years.
175 of these are marked as enhancements. Remember the bar for an
Hi All,
A *huge* thank you for all of your tremendous efforts in managing the
chaos which is FDO :) Due to all of your great work we have hit a new
milestone._*599*_! We're under 600 for the first time in years.
175 of these are marked as enhancements. Remember the bar for an
Hi Jay,
Hi All,
I had recently been listening to a podcast and they mentioned that a
linux or bsd distro would have a keyword in its bug tracking system for
bugs that are worth mentioning in the release notes. So i was thinking
that a whiteboard keyword of the same could be done so that it is
Hi Jay,
Hi All,
I had recently been listening to a podcast and they mentioned that a
linux or bsd distro would have a keyword in its bug tracking system for
bugs that are worth mentioning in the release notes. So i was thinking
that a whiteboard keyword of the same could be done so that it is
On Wed, Nov 12, 2014 at 10:13 PM, Tommy ba...@quipo.it wrote:
On Wed, 12 Nov 2014 16:24:30 +0100, Joel Madero jmadero@gmail.com
wrote:
Ok. let's go ahead with the old NEW bugs (nice oxymoron).
I suggest waiting a few days after the incoming release of LibO 4.3.4
before running
On 11/13/2014 10:05 AM, Tommy wrote:
On Thu, 13 Nov 2014 18:13:49 +0100, Joel Madero
jmadero@gmail.com wrote:
...
sure, QA consensus is necessary, however please wait the official
release
of 4.3.4 which is planned in Week 47 , Nov 17, 2014 - Nov 23, 2014
so we
are sure the user
Ok. let's go ahead with the old NEW bugs (nice oxymoron).
I suggest waiting a few days after the incoming release of LibO 4.3.4
before running this ping.
I want to wait for QA call to discuss and give the +1 also. I don't
think two of us agreeing is sufficient :-b But assuming they +1 it, I
Fixed
On 11/12/2014 12:12 PM, Tommy wrote:
see subject
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings:
http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems?
On 11/11/2014 10:42 PM, Tommy wrote:
On Wed, 05 Nov 2014 22:46:03 +0100, Robinson Tryon
bishop.robin...@gmail.com wrote:
moreover we have to decide if pinging just UNCONFIRMED old bugs or
even NEW
bugs (excluding the easy hacks).
if the ping campaign is accepted by the QA, we only
Developers don't generally accept private documents. It's better to
create a new document. If the words are the only thing that are
confidential - do a search and replace for the characters to make it
unreadable.
Best,
Joel
On 11/10/2014 02:12 PM, Viktor Mileikovskyi wrote:
Dear members!
I
Hi All,
First - a huge thank you for all of you putting in so much of your
precious time to handle the endless bugs :) Really really appreciated.
I just wanted to remind everyone that as members of QA we should do our
best to practice what we preach. That being said - every single change
in
Hi All,
I put together a simple wiki that has general tips about adding
attachments. It also has a link to a really really simple macro I put
together to strip out confidential info and instructions on how to use
it. Feel free to add more to the wiki:
Hi All,
So I'm just about done moving these around, we're down to 40 left on the
list (down from over 300 a few days ago I think). Couple questions:
_Questions
_1. What should we do about bugs that are REOPENED but unassigned? IMHO
these should be pushed back to NEW
2. Should we ping developers
Hi All,
So I'm just about done moving these around, we're down to 40 left on the
list (down from over 300 a few days ago I think). Couple questions:
_Questions
_1. What should we do about bugs that are REOPENED but unassigned? IMHO
these should be pushed back to NEW
2. Should we ping developers
Hi All,
Just wanted to point out that we have a growing list of the equivalent
of proposedEasyHack (remember we took this away per Markus'
suggestion). My first is since we left that naming scheme the list is no
longer looked at--perhaps this is wrong.
So as a reminder - whiteboard status
,
Joel Madero wrote on 04-11-14 04:47:
So I just booted about 50 bugs over to UNCONFIRMED so that list has
jumped. I'm going through the rest of the list of about 280 more bugs -
Sorry that I'm not fully aware of what's going on here, but I'm rather
annoyed by the fact that bugs that I have spend
For now I'm not doing this just because there are so many other things
to do and as of now I'm not seeing a clear message as to what we're
doingI've seen at least 3-4 proposals with different links and the
like. I suggest this be resolved on QA call, finalized, maybe a wiki
written as to what
as FIXED.
Any bug that doesn't meet the above criteria should be set to NEW (if
confirmed of course, hopefully by a third party independent person...),
or UNCONFIRMED (if not confirmed)
Best,
Joel
On 11/04/2014 07:15 AM, Joel Madero wrote:
Yes because they were set to REOPENED incorrectly. REOPENED has
Hey Robert,
Hi Joel,
Furthermore, some
of those bugs were self confirmed which we recommend against. That
being said, if a bug is confirmed and I set it to UNCONFIRMED just set
it to NEW and move onthere were 350+ bugs incorrectly set...you'll
see more moving to UNCONFIRMED if they
On 11/04/2014 07:58 AM, Cor Nouws wrote:
Joel Madero wrote on 04-11-14 16:34:
@ Cor - if you'd like you can take a look yourself and move them to NEW
Thanks for explaining Joel.
By how did they end in the wrong REOPENED state in the first place?
I have been looking at the history to see
On 11/04/2014 08:13 AM, Cor Nouws wrote:
Joel Madero wrote on 04-11-14 17:06:
On 11/04/2014 07:58 AM, Cor Nouws wrote:
Joel Madero wrote on 04-11-14 16:34:
@ Cor - if you'd like you can take a look yourself and move them to NEW
Thanks for explaining Joel.
By how did they end in the wrong
Hi All,
So I just booted about 50 bugs over to UNCONFIRMED so that list has
jumped. I'm going through the rest of the list of about 280 more bugs -
so it may climb some more. Good news isour REOPENED count is
dropping and now is reflecting more of what it's supposed to reflect
(bug assigned
Yes it has been discussed and generally agreed upon - but migration has
to happen first.
Best,
Joel
On 11/02/2014 02:16 AM, Nino Novak wrote:
Hi,
browsing through Thommy's UNCO bug list I felt the wish to know which was the
- First (oldest) known version containing the bug
- Last
I'm slightly concerned that many of these are going into NEEDINFO with
just a please test against latest release. I don't have the time to
adequately check into this right now but if someone else could look.
I've seen quite a few emails from FDO with these kinds of comments and
this would go
On 10/25/2014 02:01 AM, Nino Novak wrote:
Hi Sooraj,
Am 24.10.2014 um 11:01 schrieb sooraj kenoth:
While using the LibreOffice, I have some problems with the the
underline. In Malayalam we have a lot of stacked characters. In the
current way of drawing underline, it strikes the stacked
On 10/24/2014 02:59 AM, Jan Holesovsky wrote:
Hi,
I've seen a
Your bug was confirmed at least 1 year ago and has not had any activity
on it for over a year. Your bug is still set to NEW which means that it
is open and confirmed. It would be nice to have the bug confirmed on a
newer
On 10/24/2014 09:13 AM, bfoman wrote:
jmadero wrote
andI'm an idiot who used a bad query so now the results are going to
suck. Dammit.
Joel (annoyed with myself)
Hi!
You should change your default columns and add Changed and Number of
comments. This way you will see on Change
On 10/24/2014 02:59 AM, Jan Holesovsky wrote:
Hi,
I've seen a
Your bug was confirmed at least 1 year ago and has not had any activity
on it for over a year. Your bug is still set to NEW which means that it
is open and confirmed. It would be nice to have the bug confirmed on a
newer
On 10/17/2014 01:21 AM, Tommy wrote:
On Fri, 17 Oct 2014 07:47:05 +0200, Joel Madero
jmadero@gmail.com wrote:
I'm honestly hesitant to do any more of this kind of thing with the
email notification on. Devs hate it, users hate it, etc . . . Our bug
tracker is making progress, IMHO
I made a bad query to poke old bugs and left a comment on 75 bugs - some
of which shouldn't have been included in the query. Apologies :(
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
On 10/23/2014 12:04 AM, Sophie wrote:
Hi Joel,
Le 23/10/2014 03:41, Joel Madero a écrit :
Hi All,
We currently have *21* unconfirmed bugs that have something about
crashing involved. Would be fantastic to get these confirmed:
https://bugs.freedesktop.org/buglist.cgi?bug_status
P.S. You can query the qa-admin account for comments and see the bugs
that I touch with that account to get an idea.
could you please give a direct link... I'm not very good with bugzilla
queries :-(
I made a bad query to poke old bugs and left a comment on 75 bugs - some
of which shouldn't have been included in the query. Apologies :(
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings:
andI'm an idiot who used a bad query so now the results are going to
suck. Dammit.
Joel (annoyed with myself)
On 10/23/2014 07:40 AM, Tommy wrote:
On Thu, 23 Oct 2014 16:16:03 +0200, Joel Madero
jmadero@gmail.com wrote:
P.S. You can query the qa-admin account for comments
On 10/23/2014 01:09 PM, Tommy wrote:
On Thu, 23 Oct 2014 19:40:14 +0200, Joel Madero
jmadero@gmail.com wrote:
andI'm an idiot who used a bad query so now the results are going to
suck. Dammit.
Joel (annoyed with myself)
do you mean that you sent the retest message to bugs
Hi All,
We currently have *21* unconfirmed bugs that have something about
crashing involved. Would be fantastic to get these confirmed:
On 10/22/2014 09:58 PM, Tommy wrote:
On Sun, 19 Oct 2014 07:18:47 +0200, Robinson Tryon
bishop.robin...@gmail.com wrote:
On Sat, Oct 18, 2014 at 8:32 AM, Tommy ba...@quipo.it wrote:
For 900 (2y 6m) -- 81 bugs
On 10/17/2014 11:16 AM, Aleksandr P wrote:
Hello.
I believe that it is a good idea to check old bugs.
2014-10-16 23:00 GMT+04:00 bfoman bfo.bugm...@spamgourmet.com:
Tommy wrote
If they see the bug has gone they should mark as WORKSFORME
if bug persist they should drop a note and leave
Sounds great - so let's try to come up with a concrete plan that
everyone (or most) sign off on and then just do a thumbs up or down
vote. Let's try to not get too picky about the details.
@Tommy - you mind giving a proposed consistent plan of attack? If you
want me to briefly write something up
Okay - if you want I'll run this with my normal needinfo cleanup on the
first of the month. How's that sound?
Best,
Joel
On 10/17/2014 07:22 PM, Tommy wrote:
On Sat, 18 Oct 2014 00:30:52 +0200, Joel Madero
jmadero@gmail.com wrote:
Sounds great - so let's try to come up with a concrete
I'm a fan of doing a summary of all reported bugs for every bug reporter
in one single email that summarizes the current status, thanks them for
the continuing support, and then asks them to retest against the latest
stable. Preferably we do this around x.x.3 or so (enough time where
regressions
2014 06:26:48 +0200, Joel Madero
jmadero@gmail.com wrote:
Best,
Joel
P.S. Again I think all of this should wait until we have our own bug
tracker so we can suppress emails and not piss off everyone cc'ed on
every bug . . .
maybe we can give email notification just to the bug
@Jay -
Not so I don't think. FDO has not upgraded bugzilla (unless I missed
something). So there is a new version of bugzilla but it isn't
incorporated in FDO.
Best,
Joel
On 10/02/2014 01:27 PM, Jay Philips wrote:
Hi bfoman,
I'm assuming it rolled out yesterday or so, as since yesterday
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
101 - 200 of 999 matches
Mail list logo
