:
> >> : A visual database apps builder - http://calligra.org/kexi
> >>
> >> Qt Certified Specialist:
> >> : http://www.linkedin.com/in/jstaniek
> >>
> >> __________
but if you click on some empty space, it
should create a new text box, and allow the user to start typing.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/123554/#review85771
---
Ship it!
Ship It!
- Cyrille Berger Skott
On April 29
the repos had time to adjust to the changes.
Also, am I allowed to delete the kexi-framework* branches in the
calligra.git origin?
No but if you give me the list I can do it.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kd
d would make it possible for me to provide the correct UI for braindump.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
full history.
If I do that with calligra, my .git goes from 789MB to 209MB.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
lets not forget to coordinate the split with translation teams.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
ink we have to take the hard decision of simply killing those applications,
and keep the focus on applications that have people who care about them. And
then, for small changes, it is up to maintainers to adjust their applications.
Bigger changes should
applications.
So basically, splitting up krita from calligra? Or did I misunderstood
something?
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
On 2015-08-25 14:10, Jaroslaw Staniek wrote:
So I am assuming this as OK.
@Cyrille are you available?
This is rather a deadline for me to push a fix for defective 2.9.5/6
Kexi.
Hopefully.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
Hi,
The tag is currently on:
http://quickgit.kde.org/?p=calligra.git&a=commit&h=1a0b0efbc9104300147869a46e826a4b02e9e682
If you could give the list of bugs that have been fixed.
--
Cyrille Berger Skott
___
calligra-devel mailing list
callig
https://community.kde.org/Calligra/Schedules/2.
9/Release_Plan[1]
--
Cyrille Berger Skott
[1]
https://community.kde.org/Calligra/Schedules/2.
9/Release_Plan
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman
/kexi
Qt Certified Specialist:
: http://www.linkedin.com/in/jstaniek
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
--
Cyrille Berger Skott
to track regression caused by
porting.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
On 2015-02-26 10:23, Jaroslaw Staniek wrote:
On 26 February 2015 at 10:15, Ben Cooksley wrote:
On Thu, Feb 26, 2015 at 10:01 PM, Jaroslaw Staniek
wrote:
On 26 February 2015 at 08:31, Cyrille Berger
wrote:
On 2015-02-25 15:13, Jaroslaw Staniek wrote:
Thanks. I have one question @Cyrille
to do that.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
e note, the tag is currently set to
http://quickgit.kde.org/?p=calligra.git&a=commit&h=96ac2f8a26e628e0f8f407a90d3124c131445427
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
ause none of the
implementation or full-proof, detecting if it is the same file is apparently
hard (something to do with symlink/hardlink), there are some problems with
some network file systems and it can happen that the same header file is copied
in multiple places.
Personally, I think that "
adence and what message is sent.
No matter what, we can consider that master is re-open, and since the
translations are pointing to the right place now, there shoulde be no
problem with making changes to master.
But since this seem to disturb people, I would do the tagging tomorrow.
--
Cyril
[1] https://bugs.kde.org/show_bug.cgi?id=344012
[2] https://bugs.kde.org/show_bug.cgi?id=344346
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
--
Cyrille Be
we should do this every 3-5 days at least so that we don't end
up with
a big problem that will be difficult to unwind later.
That was the original plan, but nobody had the time to do it until now I
guess :) And that is also why we "froze" master.
--
Cy
s the
changes and any server history edit will cause them more problems.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
On Tuesday 13 January 2015 12:41:06 Inge Wallin wrote:
> So consider me back with a vengeance and I am starting to feel really well
> again. And I have missed KDE and Calligra a lot!
Welcome back, we have missed you too !
--
Cyrille Berger
ces are
> they will become unmergable.
We could open a merge window for that kind of patch right before Qt5 porting.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
Hi,
We would need to have the changelog information for 2.9 beta 2. The tag is set
on:
http://quickgit.kde.org/?p=calligra.git&a=commit&h=7fa3f5f9a63c4c6e813f6d5610d35fbefb1dd205
--
Cyrille Berger Skott
___
calligra-devel mailing list
I will do the tagging this afternoon.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
fix the problems.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
is worth porting braindump, or if it
should be rewritten from almost scratch.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
Hi,
If you can answer this email with a short list of what are the main
changes to your applications since 2.8.
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
Hi,
calligra has now been branched in calligra/2.9. Please refrain from
pushing anything to master, I am going to look into locking it tomorrow.
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-deve
but I wouldn't like to have such big change mixed
with Qt5 port...
Wouldn't that be the perfect time ?
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
On 2014-11-25 13:50, Cyrille Berger wrote:
So I would suggest:
* branch to 2.9 at beta 1
* freeze master, make it follow branch/2.9, we might even ask sysadmin
to restrict pushing to master to calligra git admins (that would be
Boudewijn and me)
* do the port in a separate branch
So what is
o calligra git admins (that would be
Boudewijn and me)
* do the port in a separate branch
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
Hi,
I have updated the wiki page with tentative schedules for 2.8.7 and 2.9:
https://community.kde.org/Calligra/Schedules/2.9/Release_Plan
https://community.kde.org/Calligra/Schedules/2.8/Release_Plan
--
Cyrille Berger Skott
___
calligra-devel
ready mentioned to Cyrille, i'd very much like to be able to get this
> in before 2.9, preferably some time before then, and essentially as soon as
> possible :)
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
t it'll be available from somewhere as well)
libqgit don't seem to be in debian at all :( That said, they should
package it we use it. And since, it is in a plugin in Gemini, maybe that
should not be a hard requirement for building gemi
l@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
Hi,
Last we talked about it, we said 2.9 for the end of this year/beginning of
next year. Should we aim for that or wait a little bit longer?
In any case, I would suggest a 2.8.7 for 3rd December with a tagging on 29th
November.
--
Cyrille Berger Skott
On 2014-09-15 09:59, Jaroslaw Staniek wrote:
Updated:
https://community.kde.org/Calligra/Schedules/2.8/Release_Plan#2.8.6
Tagging September 20
Release September 24
@Cyrille, others, please confirm it still fits your plans.
I confirm.
--
Cyrille Berger Skott
On 2014-09-01 20:14, Jaroslaw Staniek wrote:
If it does not hurt I would ask for extra 7 days.
Does not matter for me. Except I won't be able to tag on that week-end,
so lets do that on the week-end after that. Aka: tagging on 20th
September.
--
Cyrille Berger
do the tagging next week-end.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
up
That said, I am not even sure that "single repository split in multiple
tarballs" is that release manager unfriendly, and we probably can make
it so that it is not.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@k
Hi,
Sounds nice, do you know if it is possible to make the lists (or some of them)
public ?
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
On Thursday 03 July 2014 11:49:57 Dmitry Kazakov wrote:
> Oh, and we haven't backported the bugfixes for Krita yet...
There will be a 2.8.6 in august for that.
Since we have pushed 2.9.0 to December, I suggest we also add a 2.8.7 in
October.
--
Cyrille Berg
On 2014-06-30 13:26, Boudewijn Rempt wrote:
Then we probably should.
I would recommend to only do that in 'master', just to be on the safe
side.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://ma
Git commit cf804b42cb313d53729a4535622bda66951e6e42 by Cyrille Berger.
Committed on 30/06/2014 at 07:54.
Pushed by berger into branch 'calligra/2.8'.
Fix: no file formats shown in save dialogs
Backports KoFileDialog from master.
Tested on several applications, seem to work, but if so
Hi,
On 2014-06-24 14:15, Jonathan Riddell wrote:
On Tue, Jun 24, 2014 at 01:47:37PM +0200, Cyrille Berger wrote:
Hi,
Calligra 2.8.4 tarballs are available for packaging, release is
planned
for around Thursday 26th.
Ingwa is currently looking into an issue with 2.8.3 where you can't
I guess we
could schedule a 2.8.5 for early August.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
Since it is a bit tight to do the tagging during week-day, I will do that this
week-end.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
; >
> > Kexi & Calligra & KDE | http://calligra.org/kexi | http://kde.org
> > Qt for Tizen | http://qt-project.org/wiki/Tizen
> > Qt Certified Specialist | http://www.linkedin.com/in/jstaniek
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
o add:
cmake_policy(SET CMP0026 OLD)
in CMakeLists.txt, but I would not recommend adding that to
CMakeLists.txt (or if we do, have a check for the KDE version that fix
the policy warning).
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-
e and an around November 2.10
release. That would satisfy Jaroslaw and gives less reason to delay the
september release. But I guess it also depends how much new features are
coming.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-deve
n not AFK once or
so).
What is really needed is someone to work on the changelog. The best for
patch releases would be to have some automatic tool, but in lack of
that, someone who volunteer to hand collect from the changelog the
relevant item would be very appreciated.
--
Hi,
Thanks for doing the move. I have updated projects.kde.org
On 4 April 2014 00:56:52 CEST, Luigi Toscano wrote:
>Hi all,
>this is a task you usually do, but this time, in a spring cleaning
>activity,
>we moved the translations so that stable tracks 2.8 and trunk tracks
>master.
>
>Could you p
could suggest branching early august and a release
in September/October ? Or do you want a release earlier/later ?
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
hanks! I'll check the patches this weekend.
Please tell me when you have pushed, I will be tagging 2.8.1 this
week-end.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
trix.inverse();
and line 1231 with the FullPivLU can be removed.
- Cyrille Berger Skott
On March 5, 2014, 12:36 p.m., Maximiliano Curia wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://g
ck and dirty with "if (MINGW)", but we may get the problem again
later for other platforms
2) make libmso a shared library
3) compile kowv2 in the plugin and link libmso as static, but only once
(there is no real point in having kowv2 a shared library, unless it is
u
e, that for some reasons, it seems to only happen with a
clean build.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
Hi,
Given Dmitry's long list of bugs, I was wondering about making a beta 3
(tagging this week-end or next week-end). Anyone has any objections ?
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kd
r
changes (features and bug fixes) that have happen in your
applications since 2.7 !
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
On Sunday 24 November 2013 01:01:01 Jaroslaw Staniek wrote:
> On 23 November 2013 10:48, Cyrille Berger Skott
wrote:
> > Since we had some important bug fixes, I will tag Calligra 2.7.5
tomorrow
> > for a release shortly after that.
>
> Cool, coincidentally, that'
Hi,
Since we had some important bug fixes, I will
tag Calligra 2.7.5 tomorrow for a release
shortly after that.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
On 2013-11-20 05:10, Yuë Liu wrote:
On Tue, Nov 19, 2013 at 3:54 AM, Boudewijn Rempt
wrote:
On Sunday 17 November 2013 Nov 18:21:21 Cyrille Berger wrote:
I would suggest to push by a week then, if no one object.
I'm fine with that. I doubt I'll manage to get my branch (the mvc o
I would suggest to push by a week then, if no one object.
Inge Wallin wrote:
>___
>calligra-devel mailing list
>calligra-devel@kde.org
>https://mail.kde.org/mailman/listinfo/calligra-devel
___
calligra-devel
Hello,
Reminder branching for 2.8 release will happen next week.
I have updated the wiki with the release plan:
http://community.kde.org/Calligra/Schedules/2.8/Release_Plan
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel
setup instructions for
a mirror?
Thank you very much in advance for answering my question.
Kind regards
Timo Jacob
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
--
Cyrille Berger
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/113784/#review43347
---
Ship it!
Ship It!
- Cyrille Berger Skott
On Nov. 10, 2013
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
Yes, never rebase commits that have already been pushed (git should not
even let you do that), and yes the calligra policy is to merge-squash.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman
ooks like we'll have some nice additions to Words
as well.
Thoughts?
I think this is very reasonable.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
I am done. Hopefully it should be in order.
On Saturday 10 August 2013 06:43:27 Cyrille Berger Skott wrote:
> Hi,
>
> I am about to switch branches for translations of calligra:
> * trunk -> master
> * branch/stable -> calligra/2.7
>
> To translators, if you see you
ll fail and have to
be restarted from the beginning, I will send an other email
when I am finished.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
es/2.7/Release
_Plan
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
burden of porting on a
fewer set of people.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
Url& _url);
};
And then have two implementations, one for KIO (used on Linux) and one
using QFile. I guess this might be moved in the future to KF, as I guess
many more KDE Applications who wants portability don't really care about
all the features of KIO's API, and just want to read fil
e use (no
matter how much Qt/KF is an important dependency). It is more
importantly used for communication.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
rt
As for the problem of users using master, you have two alternatives:
* tell them to not update
* freeze "master" (as in no commits, except for compile fix) and then
use a different branch name for porting. After all "master" is just an
othe
2.7.x (provided I don't forget
about it, since it is a manual process...)
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
t's
going on right now...
Yes, tuesday or wednesday seems to be the best days.
Is that
.org/?p=calligra.git&a=commit&h=1c70852b6328b32e448ee56ba52ea60ca404beba
?
In any case, I will tag 2.7.1 tomorrow.
--
Cyri
2.7.0
* tag 2.7.1
* and announce 2.7.1 (it might sounds confusing, but this is the best
way to know that users will get the fixed version)
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo
is
working on it and have a solution coming soon, we would have to ignore
that bug.
SO my suggestion would:
* tag final July 12th
* release final July 17th
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mai
ether the plugin still worked or
whether we need more work to make it do stuff...
So, hands up who's got a space navigator!
I have one. I tested it not so long ago. And it still "works", except it
is extremely sensitive.
--
Cyrille Berger Skott
On 2013-06-09 20:38, Elvis Stansvik wrote:
2013/6/9 Cyrille Berger Skott
On Sunday 09 Jun 2013, Boudewijn Rempt wrote:
On Thursday 30 May 2013 May 14:57:04 Cyrille Berger wrote:
> Hi,
>
> Don't forget to mark the bugs that are release blocker as such
in
> bugs.kde.org [1]
uld
probably require a couple of beta. Anyone objecting to disabling
autosave ?
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
On Sunday 09 Jun 2013, Boudewijn Rempt wrote:
> On Thursday 30 May 2013 May 14:57:04 Cyrille Berger wrote:
> > Hi,
> >
> > Don't forget to mark the bugs that are release blocker as such in
> > bugs.kde.org, currently there are four release blockers:
> >
&g
e.org/Calligra/Schedules/Release_Blockers#Link_to_Release_critical_bugs)
If that list does not drop to 0, I will tag an other beta next week.
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
kdepim ;))
--
Cyrille Berger Skott
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
Since we have the beta 2 for 2.7 coming next week, I would suggest doing 2.6.4
the week after that.
Jaroslaw Staniek wrote:
>Hi,
>We tagged, uploaded 2.6.3 in April but not announced. Tiny changelog,
>but we need to announce, right?
>I fixed this today :/
>
>Secondly, I'd like to ask for taggin
Christian Muehlhaeuser
* Copyright (c) 2004-2006 Seb Ruiz
* Copyright (c) 2004,2005 Max Howell
* Copyright (c) 2005 Gabor Lehel
* Copyright (c) 2008,2009 Mark Kretschmann
What should i do with this problem?
ask all the people above if they would agree with relicensing to LGPL.
--
Cyri
Hi,
With a few days delay (sorry about that, I got distracted by the first
week-end of spring), master has been branched.
The branch is called "calligra/2.7". The hash for the first beta tag is
748ab369f503cac0108a9b54fd2d44422c0901cd.
--
Cyrille Be
> On April 21, 2013, 6:15 a.m., Cyrille Berger Skott wrote:
> > Ship It!
But if you could add some documentation explaining the use of:
KoColorConversionTransformation::InternalRenderingIntent
KoColorConversionTransformation::InternalConversionFlags
KoColorConversionTrans
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/110087/#review31360
---
Ship it!
Ship It!
- Cyrille Berger Skott
On April 20, 2013
Hi,
This a reminder that the 2.7 branching is coming soon next week. Please do not
hurry to merge, and only merge what is ready, that way we can keep 2.7 testing
cycle short and make 2.8 happen sooner.
http://community.kde.org/Calligra/Schedules/2.7/Release_Plan
--
Cyrille Berger Skott
no harm in removing the
slots, so thanks for the patch and go ahead for the commit.
- Cyrille Berger Skott
On April 6, 2013, 8:33 p.m., Friedrich W. H. Kossebau wrote:
>
> ---
> This is an automatically generated e-mail. To rep
y defined by people who do the work
(like in KDE). So most likely, you would be doing the signing within the
Android "subcommitee" of the release team, which is where it belongs. So I
don't see why they would refuse.
--
Cyrille Berger Skott
___
it (sysad...@kde.org or
#kde-sysadmin on freenode), and if they don't want to handle it, we
could have a calligra account with several trusted people having access
to the key. However, I would suggest waiting to have a stable version,
before using a more official account.
--
Cyrille B
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109666/#review29805
---
Ship it!
Ship It!
- Cyrille Berger Skott
On March 22, 2013
On 2013-03-22 14:46, Cyrille Berger wrote:
On 2013-03-21 22:51, Friedrich W. H. Kossebau wrote:
If so, would you blog about this yourself? Or could you give some
cite which I
could use in a blog post of mine? Perhaps some additional ideas (or
inspiring
mockups) you have, to help people get the
1 - 100 of 520 matches
Mail list logo
