On 17 May 2017 at 22:47, Fan Zhang wrote:
> I was asked for a username and password from ftp://ftp.lyx.org
>
> I don’t know how I can get that. Can you please help?
>
Hi Fan,
Thanks for letting us know you still have the problem. I think I was able
to reproduce your
On 15 May 2017 at 10:07, Kornel Benko wrote:
> What's wrong with Colour? Are we supposed to use US English only?
> It compiles with cmake build.
>
I'm fine with using British English, generally speaking I actually prefer
it to be honest...
It was just a wild guess from my side
On 15 May 2017 at 01:00, Scott Kostyshak wrote:
> The following page is still not "secure" (according to Chromium):
>
> https://www.lyx.org/Download
>
Oh... I missed this was for the web site, which is actually also a wiki of
the same kind (PmWiki), but a different instance.
Does everyone get an automatic reply from the account below when posting to
lyx-devel, and if so, should we ask Maté to remove him from the list...?
Alternatively I suppose I could create a filter to get rid of his auto
reply, but that just solves the issue for me.
/C
PS. Google translate says it
On 15 May 2017 at 03:28, wrote:
> setMessageColour(
Did someone type ...Colour( instead of Color(?
/C
On 3 May 2017 at 13:26, Scott Kostyshak wrote:
> Bump. It would be nice to at least have
>
> https://www.lyx.org/Download
>
> provide a secure connection for the final release. I would normally
> propose this as a release blocker, but since we've only implemented
> https
Hi
We already have CI jobs that run tasks on branch master. We'll keep them
running of course, and likely add more jobs.
However, do we at some future point also want CI jobs that run based on a
branch/branches related to the upcoming release?
Sorry for being a bit imprecise here, but I think
On 8 April 2017 at 16:24, Kornel Benko <kor...@lyx.org> wrote:
> Am Samstag, 8. April 2017 um 15:46:54, schrieb Christian Ridderström <
> c...@lyx.org>
> > On 8 April 2017 at 11:49, <ci-...@inria.fr> wrote:
> >
> > I think this is real breakage
Apologies for only sending to Jean-Marc initially. I end up doing this
mistake a lot with gmail these days.
/C
-- Forwarded message --
From: Christian Ridderström <c...@lyx.org>
Date: 8 April 2017 at 16:06
Subject: Re: Doxygen sourcedoc: Should there be a non-empty "
On 8 April 2017 at 11:49, wrote:
> make[4]: Leaving directory '/build/workspace/src'
> make check-TESTS
> make[4]: Entering directory '/build/workspace/src'
> make[5]: Entering directory '/build/workspace/src'
> PASS: tests/test_ExternalTransforms
> PASS:
On 6 April 2017 at 13:47, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote:
> Le 04/04/2017 à 22:08, Christian Ridderström a écrit :
>
>> Hi,
>>
>> Should the Doxygen docs have a "main page"? At
>> https://www.lyx.org/sourcedoc/latest/index.htm
On 6 April 2017 at 19:45, Jean-Marc Lasgouttes wrote:
> I did that. Please remove your own patch.
>
I've modified the CI job to not apply _your_ patch ;-)
I've also started a new build, so in an hour or two we should see that it
works.
Thanks,
/C
On 28 February 2017 at 03:24, Pavel Sanda <sa...@lyx.org> wrote:
> Christian Ridderström wrote:
> > Currently we're also keeping all the previously generated "sourcedocs".
> > There I'm guessing we at most would like to keep a few, or perhaps none.
>
> I
Hi,
Should the Doxygen docs have a "main page"? At
https://www.lyx.org/sourcedoc/latest/index.html
the main page is currently empty.
I don't know if this is an error on my side, or if we simply haven't
created a main page.
/Christian
On 28 March 2017 at 11:52, Jean-Marc Lasgouttes wrote:
> Le 25/03/2017 à 14:07, ci-...@inria.fr a écrit :
>
>> https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xen
>> ial-qt4-autotools-extended/118/
>>
>>
> Christian, did you do something to have it back to normal ?
>
On 21 March 2017 at 21:11, Christian Ridderström <c...@lyx.org> wrote:
> I think I primarily want to make the CI workers have more disk space, as I
> think we in general would like to keep e.g. the workspace of the last
> successful build, and at the same time have more than f
On 21 March 2017 at 15:48, Scott Kostyshak wrote:
> > If anyone's interested, you can see remaining disk space (_if logged in_)
> > for the CI workers at this link:
> > https://ci.inria.fr/lyx/computer/
>
> Would it be possible and desirable to have an email sent to the
>
On Mon, 6 Feb 2017 at 11:44, Jean-Marc Lasgouttes
wrote:
>
> We could boldly (!) declare that we rely on automake 1.14 (Jun 2013),
> since only developers (on antique systems like mine) would have to adapt.
I believe this is the thread with the patch in question, related to
On 20 March 2017 at 07:11, Guillaume MM wrote:
> What is this patch that fixes make distcheck? Can it be applied in master?
I've found the thread with the patch (by searching for Fix-distclean-for
-recent-automake-versions) and did a reply in that thread, better discussed
there I
Hi,
Just want to let you know that some of the CI jobs simply failed because
the CI workers ran out of disk space. Some CI jobs take 4 GB, and with no
remaining workdirs from CI jobs, the total disk space per slave is about 20
GB. Anyway, I've done some cleaning and this aspect should be back to
On 19 March 2017 at 12:14, Christian Ridderström <c...@lyx.org> wrote:
>
> But I think someone should take a log at the error output and see if they
> can figure out why it's breaking, I think it's a real breakage.
>
Could perhaps the following line in the CI job's config
On 18 March 2017 at 22:20, Christian Ridderström <c...@lyx.org> wrote:
> Christian, does the check start from a fresh tree? If you do 'make
>>> clean' and the rules have changed, it might be that some .o files remain
>>> at the wrong place
>>>
>>
>&
On 7 March 2017 at 11:23, Jean-Marc Lasgouttes wrote:
> Hi Christian,
>
> The next natural step could be to use your CI stuff to update our coverity
> builds:
> https://scan.coverity.com/projects/4164
>
> Currently the build are submitted by hand by Liviu or recently by
On 18 March 2017 at 16:46, Christian Ridderström <c...@lyx.org> wrote:
> Christian, does the check start from a fresh tree? If you do 'make
>> clean' and the rules have changed, it might be that some .o files remain
>> at the wrong place
>>
>
> I think most CI
On Fri, 17 Mar 2017 at 21:10, Jean-Marc Lasgouttes
wrote:
> Le 15/03/2017 à 12:12, Kornel Benko a écrit :
> > Probably some automake failure. Using old
> ./src/support/tests/dummy_functions.o in the build dir.
> > Removing that file, it will be rebuild with
> > make
On 27 February 2017 at 17:34, Jean-Pierre Chrétien <
jeanpierre.chret...@free.fr> wrote:
> I proposed recently to add something about this, as I made a list of
>> dependencies that are not in TL.
>>
>
> In fact, you may check the thread beginning with this message:
>
>
Apologies, accidentally sent only to Kornel rather than the list, reposting
now.
On 27 February 2017 at 09:18, Kornel Benko wrote:
> > https://ci.inria.fr/lyx/job/testing-Jenkins/job/ctest/
> lastCompletedBuild/testReport/
>
> Looking inside this I see for instance in the first
Hi,
This is a CI job I'm working on that's intended to run automated tests:
https://ci.inria.fr/lyx/job/testing-Jenkins/job/ctest/
Currently there's about 2300 failing tests (out of 6000), so I'm guessing
more stuff needs to be installed.
Detailed results via this link:
Hi,
I just want to let people know that (hopefully) we now have a working
pipeline where:
- A CI job [1] on Mondays, builds and uses Doxygen to generate "sourcedoc"
- The LyX server, on Tuesdays, then pulls in and deploys the "sourcedoc" as
https://www.lyx.org/sourcedoc/latest/
We'll see
On 18 February 2017 at 09:18, Pavel Sanda <sa...@lyx.org> wrote:
> > > Christian Ridderström wrote:
> > > > But some HTML-stuff doesn't look right when served from the CI
> server, so
> > > > I've placed a copy for review on the lyx server here:
&g
On 14 February 2017 at 01:17, Pavel Sanda <sa...@lyx.org> wrote:
> Christian Ridderström wrote:
> > But some HTML-stuff doesn't look right when served from the CI server, so
> > I've placed a copy for review on the lyx server here:
> >http://www.lyx.org/test
Not sure this made it to the list earlier, so resending.
On 2 February 2017 at 17:37, Christian Ridderström <c...@lyx.org> wrote:
> Hi,
>>>
>>> I thought I'd setup a CI job that generates doxygen, i.e. do:
>>> make doxygen
>>>
On 13 February 2017 at 22:06, Pavel Sanda wrote:
> > If someone has instructions on how to build on some other platform, i.e.
> > not Ubuntu..., let me know and I can set up such a job.
>
> You have list of available distros or you need to build your own image?
I think pretty
On 27 January 2017 at 20:11, Pavel Sanda wrote:
>
> as an additional safety meaure I would like to track our .sig files stored
> on
> ftp via git. Is there any opposition to put them into master/development?
Sounds like a good idea to me.
Could you give an example of where in
Hi,
Using Jean-Marc's patch to get 'make distcheck' to work with a later
version of autoconf, I've now gotten this CI job to pass:
https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/
The job applies Jean-Marc's patch at the beginning [*], and then proceeds
On 24 January 2017 at 10:25, Pavel Sanda wrote:
> > The job that builds with autotools and qt4 fails during 'make distclean'
> > within 'make distcheck'.
> > Here's a link to the console output:
>
> I looked into the issue and it is caused by the fact that you use new
> autotools
Accidentally hit "send"... finishing e-mail now:
On 23 January 2017 at 23:26, Christian Ridderström <c...@lyx.org> wrote:
> Hi,
>
> I've tested to compile LyX locally using one of the Docker containers,
> i.e. I was on a mac and used the Docker image
> "bui
Hi,
I've tested to compile LyX locally using one of the Docker containers, i.e.
I was on a mac and used the Docker image
"build-lyx-using-ubuntu-latest-qt5-cmake" to build LyX as if the build was
done in a Ubuntu environment.
In case anyone would like to test this (e.g. to better be able to help
Hi,
When building LyX using CMake (and Qt5), the resulting source packages (?)
are empty, which seems wrong to me... See e.g. the "workspace" of this job:
https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-latest-qt5-cmake/ws/build/
E.g., the file "LyX-2.3.tar.gz
FYI, this was me fiddling with something.
/Christian
On 22 January 2017 at 04:53, wrote:
> https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-
> latest-qt5-cmake/12/Changes:
>
> [forenr] Allow to properly scale the GUI with Qt5
>
>
ve copied in the last part of the output at the end of this email
The setup of the Docker container (sort of a light weight VM) that contains
the build environment can be seen here:
https://github.com/DrChr/build-lyx-using-ubuntu-xenial-qt4-autotools/blob/master/Dockerfile
but it's just these steps:
FR
On 19 January 2017 at 23:58, Pavel Sanda <sa...@lyx.org> wrote:
> Christian Ridderström wrote:
> > When a CI job is using e-mail notifications, there's an option to in
> > addition to e-mailing the devel-list, also e-mail individuals who
> recently
> > committed. Do
On 19 January 2017 at 20:57, Pavel Sanda wrote:
>
> If you want test cmake as well you can, but please run autotools, I am
> going to debug
> primarily that.
>
I actually wanted to test building with Qt5, but I couldn't (easily) get it
to work with autotools...
I assume I'm
On 19 January 2017 at 16:30, Kornel Benko wrote:
> > # Change directory to folder with cloned LyX repository
>
> Clone is not needed normally iff used only by cmake.
>
The cloning is automatically done by the CI server / CI job, pulling the
latest changes from git.lyx.org.
>
Hi,
When a CI job is using e-mail notifications, there's an option to in
addition to e-mailing the devel-list, also e-mail individuals who recently
committed. Do we want that?
Note: The CI server will extract the e-mail addresses of the individiuals
from the Git commits.
/Christian
PS.
Here's
FYI, I forced this build to fail intentionally to trigger this e-mail (I
SSH'd to the CI worker and deleted the src/-folder while CMake was
running...).
I'll for now activate e-mails to the devel-list for the two jobs that
builds from master.
/Christian
On 19 January 2017 at 23:32,
FYI, this was an e-mail from the CI server (which runs the software called
"Jenkins") which I sent to verify that the CI server is now able to mail
the lyx-devel-list.
/Christian
PS.
I'll now configure one of the CI jobs to mail the devel-list when the jobs
fails, and I'll also make the job fail
build
cd build
CMAKE_OPTS="-DLYX_USE_QT=QT5 -DLYX_CPACK=ON -DCPACK_SOURCE_TGZ:BOOL=ON"
cmake $CMAKE_OPTS .. && make && make package_source
This will build LyX and only then do 'make package_source'. Anything else
that should be in there?
/Christian
> Kornel
>
>
--
Christian Ridderström, +46-70 687 39 44
On 19 January 2017 at 03:53, Pavel Sanda <sa...@lyx.org> wrote:
> Christian Ridderström wrote:
> > The Jenkins SW is capable of sending an e-mail, I just tested to two of
> my
> > e-mail addresses.
> > But to where should e-mails be sent - lyx-devel-list?
>
> I
0dev
distdir=../lyx-2.3.0dev/autotests \
am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=:
distdir)
make[2]: Entering directory '/usr/src/lyx/autotests'
make[2]: *** No rule to make target 'export/ja/wrong_auto_encoding.lyx',
needed by 'distdir'. Stop.
make[2]: Leaving directory '/usr/src/lyx/autotests'
Makefile:674: recipe for target 'distdir' failed
make[1]: *** [distdir] Error 1
make[1]: Leaving directory '/usr/src/lyx'
Makefile:772: recipe for target 'dist' failed
make: *** [dist] Error 2
--
Christian Ridderström, +46-70 687 39 44
list if error was found.
>
There seems to be RSS feeds available right now (see bottom right corner of
https://ci.inria.fr/lyx/ ) that I was able to add to my RSS reader (
http://theoldreader.com) . It's probably also possible to get the CI server
to send e-mail notifications to lyx-devel, assuming we want that?
/Christian
--
Christian Ridderström, +46-70 687 39 44
r runs out of disk space.. But someday a build will perhaps
fail due to bad LyX code, in which case we could catch it. The CI system
should build on more configurations, and probably build more branches than
just 'master'. And it should also be running test cases.
--
Christian Ridderström, +46-70 687 39 44
On 18 January 2017 at 01:21, Scott Kostyshak <skost...@lyx.org> wrote:
> On Tue, Jan 17, 2017 at 11:54:02PM +0100, Christian Ridderström wrote:
> > Hi,
> >
> > Does anyone have a list of the build dependencies that need to be
> installed
> > in order to bu
,
Christian
--
Christian Ridderström, +46-70 687 39 44
the web site ought to
primarily be a matter of using the wiki functionality (for both of them).
Do you have the login passwords?
Regards,
Christian
--
Christian Ridderström, +46-70 687 39 44
> Comment (by skostysh):
>
> Seems that now might be a good time to look into it:
>
> https://letsencrypt.org/2015/11/12/public-beta-timing.html?v=2
>
> --
> Ticket URL: <http://www.lyx.org/trac/ticket/9873#comment:7>
> The LyX Project <http://www.lyx.org/>
it secure.
--
Christian Ridderström, +46-70 687 39 44
as I'm a
novice at this and I want it secure.
--
Christian Ridderström, +46-70 687 39 44
I can edit the parent page[2] with the LyX password but not the
child page[1]. How can I contribute to the wiki?
Best Regards,
MB
[1] http://wiki.lyx.org/Layouts/SongbookInstall
[2] http://wiki.lyx.org/Layouts/Songbook
--
Christian Ridderström, +46-70 687 39 44
ent
> LyX versions.
>
> Now I can edit the parent page[2] with the "LyX" password but not the
> child page[1]. How can I contribute to the wiki?
>
> Best Regards,
> MB
>
> [1] http://wiki.lyx.org/Layouts/SongbookInstall
> [2] http://wiki.lyx.org/Layouts/Songbook
>
>
--
Christian Ridderström, +46-70 687 39 44
the upload page
give new/updated instructions.
Tahnks,
Christian
--
Christian Ridderström, Cell phone: +46-70 687 39 44
on the server. Not sure we want that in this particular
case.
However, some URL redirection magic could probably be made to work so that
/uploads/ or some other path points into the Trac-tree.
Once the other stuff is up and running I can look at the redirection issue.
/Christian
--
Christian
e.
>
> Could you please have a look? Thanks!
> Pavel
>
Let's do the upload page once the rest is in place, and let the upload page
give new/updated instructions.
Tahnks,
Christian
--
Christian Ridderström, Cell phone: +46-70 687 39 44
Christian
--
Christian Ridderström, Cell phone: +46-70 687 39 44
://www.lyx.org/trac/ticket/8298#comment:2
The LyX Project http://www.lyx.org/
LyX -- The Document Processor
--
Christian Ridderström, Cell phone: +46-70 687 39 44
gt;
> Hi Christian!
> Do you have idea what is going on?
>
> --
> Ticket URL: <http://www.lyx.org/trac/ticket/8298#comment:2>
> The LyX Project <http://www.lyx.org/>
> LyX -- The Document Processor
>
--
Christian Ridderström, Cell phone: +46-70 687 39 44
anyone know of an easy way to bottom post in gmail? (I'm
using Opera, not Firefox)
--
Christian Ridderström, Cell phone: +46-70 687 39 44
wn repository, would that become an issue?
regards,
Christian
PS. Does anyone know of an easy way to bottom post in gmail? (I'm
using Opera, not Firefox)
--
Christian Ridderström, Cell phone: +46-70 687 39 44
is
that it doesn't matter as the cell phone number is very easily found
online, e.g. in the yellow pages in Sweden. My reasoning could be
wrong here of course!
Regards,
Christian
On 1 June 2011 11:47, Abdel Younes you...@lyx.org wrote:
On May 31, 2011, at 11:18 PM, Christian Ridderström wrote:
Hi,
I'm
is
that it doesn't matter as the cell phone number is very easily found
online, e.g. in the "yellow pages" in Sweden. My reasoning could be
wrong here of course!
Regards,
Christian
On 1 June 2011 11:47, Abdel Younes <you...@lyx.org> wrote:
> On May 31, 2011, at 11:18 PM, Christia
Hi,
I'm trying to figure out if my mails get through or not...
/Christian
--
Christian Ridderström, Cell phone: +46-70 687 39 44
Hi,
I'm trying to figure out if my mails get through or not...
/Christian
--
Christian Ridderström, Cell phone: +46-70 687 39 44
On 19 March 2010 16:16, rgheck rgh...@bobjweil.com wrote:
On 03/19/2010 10:57 AM, Chris Reynolds wrote:
Hello Abdel,
I think I got a few placement suggestions from your Colleagues however, I
was a bit puzzled as to what they suggested. Maybe you can show me a
preview picture or set it up on
Basically, we're talking about having a contributors section where we can
mention people who've given us money.
I must be missing something... I changed the web (i.e. wiki) page and
did the following:
* Added a table of contents in the beginning
* Added a heading 'Contributors' for the normalä
On 19 March 2010 19:43, Chris Reynolds ch...@webhostingsearch.com wrote:
Hello Christian, nice to meet you BTW :)
I think that this could work if you changed the title to Supporters or
External Supporters. I will check this with our manager and see what he
would prefer, because the final
On 19 March 2010 16:16, rgheck wrote:
> On 03/19/2010 10:57 AM, Chris Reynolds wrote:
>>
>> Hello Abdel,
>>
>> I think I got a few placement suggestions from your Colleagues however, I
>> was a bit puzzled as to what they suggested. Maybe you can show me a
>> preview picture
> Basically, we're talking about having a "contributors" section where we can
> mention people who've given us money.
I must be missing something... I changed the web (i.e. wiki) page and
did the following:
* Added a table of contents in the beginning
* Added a heading 'Contributors' for the
On 19 March 2010 19:43, Chris Reynolds wrote:
> Hello Christian, nice to meet you BTW :)
>
> I think that this could work if you changed the title to "Supporters" or
> "External Supporters". I will check this with our manager and see what he
> would prefer, because the
* Finally, if you have shell access to the server, modify the file:
...
If you don't have access, just tell me.
Hi Pavel,
I was unclear,. If you don't have access, I suggested that you tell me
the name of the page to which you have added a password, so that I
could then add that name to the
>> * Finally, if you have shell access to the server, modify the file:
...
>> If you don't have access, just tell me.
Hi Pavel,
I was unclear,. If you don't have access, I suggested that you tell me
the name of the page to which you have added a password, so that I
could then add that name to
It's done now.
In order to protect a page from editing with a password, you do as follows:
* Go to the page, with '?action=attr' appended to the URL, e.g.
http://wiki.lyx.org/Layouts.SongbookInstall?action=attr
Then you'll see fields where you can set a password,
and in this case we
It's done now.
In order to protect a page from editing with a password, you do as follows:
* Go to the page, with '?action=attr' appended to the URL, e.g.
http://wiki.lyx.org/Layouts.SongbookInstall?action=attr
Then you'll see fields where you can set a password,
and in this case we
I've manually generated and moved the doxydocumentation.
/Christian
I've manually generated and moved the doxydocumentation.
/Christian
2010/1/8 Uwe Stöhr uwesto...@web.de:
Vincent van Ravesteijn schrieb:
Is there a way to give us developers a way to delete pages or do already
another developer have this right (in case you are not available due to your
excessive vacations ;-) )?
http://wiki.lyx.org/PmWiki/DeletingPages
2010/1/9 Pavel Sanda sa...@lyx.org:
Christian Ridderström wrote:
Is there a way to give us developers a way to delete pages or do already
another developer have this right (in case you are not available due to
your
excessive vacations ;-) )?
http://wiki.lyx.org/PmWiki/DeletingPages
That's my fault, I started doing it but stopped when I was unable to
compile. Something related to Qt.
I'll repost the error message, I assume a dependency is missing or something.
Well, the previous error seems to have vanished now that I updated the sources.
However, doxygen fails because
2010/1/8 Uwe Stöhr :
> Vincent van Ravesteijn schrieb:
>
>>> Is there a way to give us developers a way to delete pages or do already
>>> another developer have this right (in case you are not available due to your
>>> excessive vacations ;-) )?
>
>>
2010/1/9 Pavel Sanda <sa...@lyx.org>:
> Christian Ridderström wrote:
>> >>> Is there a way to give us developers a way to delete pages or do already
>> >>> another developer have this right (in case you are not available due to
>> >>>
> That's my fault, I started doing it but stopped when I was unable to
> compile. Something related to Qt.
>
> I'll repost the error message, I assume a dependency is missing or something.
Well, the previous error seems to have vanished now that I updated the sources.
However, doxygen fails
2009/12/21 Vincent van Ravesteijn - TNW v.f.vanraveste...@tudelft.nl:
Christian, you're listed as a contributor to dvipng (so you must be an
expert). Do you have any info on this ?
Sorry, I don't have any idea at all about this. (Actually, I wonder if
you're talking to the right Christian:-)
2009/12/21 Vincent van Ravesteijn - TNW :
>
> Christian, you're listed as a contributor to dvipng (so you must be an
> expert). Do you have any info on this ?
Sorry, I don't have any idea at all about this. (Actually, I wonder if
you're talking to the right
recently.
I have a vague memory that this code was sensitive to an extra line break
at the end... could that be related to the change in props?
/C
--
Christian Ridderström +46 70 687 39 44
recently.
Umm... I looked at the web page, it doesn't seem broken to me?
(I don't think I've done anything)
/C
--
Christian Ridderström +46 70 687 39 44
recently.
I have a vague memory that this code was sensitive to an extra line break
at the end... could that be related to the change in props?
/C
--
Christian Ridderström +46 70 687 39 44
recently.
Umm... I looked at the web page, it doesn't seem broken to me?
(I don't think I've done anything)
/C
--
Christian Ridderström +46 70 687 39 44
communication, maybe I never will)
Now, in order for other LyX developers to have the opportunity to see
what's possible in Wave, you need an account, for which you need an
invite.
Christian Ridderström wrote:
feeling for how easy, or difficult, it is to work on one document when
communication, maybe I never will)
Now, in order for other LyX developers to have the opportunity to see
what's possible in Wave, you need an account, for which you need an
invite.
Christian Ridderström wrote:
feeling for how easy, or difficult, it is to work on one document when
Hi Uwe,
(my apologies for posting part of your reply to the list, but I think
it might good if I explain in general why I passed on invitations)
Use it or not as you please. My main motivation for giving you the
invite is that the collaborative aspects with using google wave is
something I
2009/12/8 Jean-Marc Lasgouttes lasgout...@lyx.org:
Le 8 déc. 09 à 21:10, Christian Ridderström a écrit :
(my apologies for posting part of your reply to the list, but I think
it might good if I explain in general why I passed on invitations)
I think passing the invitation was a good idea
101 - 200 of 1976 matches
Mail list logo