Am Sonntag, dem 13.02.2022 um 04:19 +0100 schrieb Thibaut Cuvelier:
> You mean, with code like
> https://github.com/cburschka/lyx/blob/d3c335a5d524e2edeb73ae1a891fcc58ba5bfd1a/src/BiblioInfo.cpp#L421-L428
> for the search? I thought it would be good to have a file to store
> this information, but I
e.asc
> Type: application/pgp-signature
> Size: 488 bytes
> Desc: This is a digitally signed message part
> URL: <
> http://lists.lyx.org/pipermail/lyx-cvs/attachments/20220209/980878f0/attachment-0001.asc
> >
>
You mean, with code like
https://github.com/cburschka/lyx/blo
Am Sun, 1 Mar 2020 11:02:28 -0500
schrieb Richard Kimberly Heck :
> On 3/1/20 10:55 AM, Kornel Benko wrote:
> > Renamig does not show in lyx-CVS
> > Your mail to 'lyx-cvs' with the subject
> >
> > [LyX/master] Moving 3rdparty/evince_sync to
> > 3r
On 3/1/20 10:55 AM, Kornel Benko wrote:
> Renamig does not show in lyx-CVS
> Your mail to 'lyx-cvs' with the subject
>
> [LyX/master] Moving 3rdparty/evince_sync to
> 3rdparty/scripts/evince_sync
>
> Is being held until the list moderator can review it for appro
Renamig does not show in lyx-CVS
Kornel
--- Begin Message ---
Your mail to 'lyx-cvs' with the subject
[LyX/master] Moving 3rdparty/evince_sync to
3rdparty/scripts/evince_sync
Is being held until the list moderator can review it for approval.
The reason it is
Am 10.01.2018 um 09:57 schrieb Pavel Sanda:
Change your git config, so your commiter name is not uwesto...@web.de but
uwesto...@lyx.org .
Many thanks Pavel. I did this now. I see that my lyx.org address is
already subscribed to lyx-cvs. I see that all mails from lyx-cvs are
automatically
Uwe Stöhr wrote:
> What do others do? I mean I don't like to get a mail for every commit since
Change your git config, so your commiter name is not uwesto...@web.de but
uwesto...@lyx.org .
https://help.github.com/articles/setting-your-commit-email-address-in-git/
Pavel
;m afraid I wasn't able to deliver your message to the following addresses.
> This is a permanent error; I've given up. Sorry it didn't work out.
>:
> Sorry, only subscribers may post. If you are a subscriber, please
> forward this message to lyx-cvs-ow...@lists.lyx.or
following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
:
Sorry, only subscribers may post. If you are a subscriber, please
forward this message to lyx-cvs-ow...@lists.lyx.org to get your new
address included.
I cannot remember that I had to be a subsc
On Tue, Jun 06, 2017 at 05:29:52PM -0400, Richard Heck wrote:
> I checked the last 1000 commits to 2.2.x, and setting the limit to 32000
> failed to send a complete commit log for only one commit for which you
> might want it: 54248a6e
The patch file for this commit is 34K in case someone was won
On 06/06/2017 05:04 PM, Richard Heck wrote:
> On 06/06/2017 03:35 PM, Scott Kostyshak wrote:
>> On Sun, Jun 04, 2017 at 10:58:52PM -0400, Richard Heck wrote:
>>> On 06/04/2017 09:02 PM, Scott Kostyshak wrote:
>>>> Commit 52eee8e5 ("Fix .po files") was n
On 06/06/2017 03:35 PM, Scott Kostyshak wrote:
> On Sun, Jun 04, 2017 at 10:58:52PM -0400, Richard Heck wrote:
>> On 06/04/2017 09:02 PM, Scott Kostyshak wrote:
>>> Commit 52eee8e5 ("Fix .po files") was not sent to lyx-cvs. I imagine it
>>> is because the
On Sun, Jun 04, 2017 at 10:58:52PM -0400, Richard Heck wrote:
> On 06/04/2017 09:02 PM, Scott Kostyshak wrote:
> > Commit 52eee8e5 ("Fix .po files") was not sent to lyx-cvs. I imagine it
> > is because the commit is 13MB. I think it is a good decision not to send
>
On 06/04/2017 09:02 PM, Scott Kostyshak wrote:
> Commit 52eee8e5 ("Fix .po files") was not sent to lyx-cvs. I imagine it
> is because the commit is 13MB. I think it is a good decision not to send
> patches that are too large, but it would be nice to receive at least the
>
Commit 52eee8e5 ("Fix .po files") was not sent to lyx-cvs. I imagine it
is because the commit is 13MB. I think it is a good decision not to send
patches that are too large, but it would be nice to receive at least the
commit message and the stats (which files were changed), and possibly
wever with only 3 changes this
> > time,
> > instead of ~ a hundred the last time).
> >
> > We'll see what mails lyx-devel will get from cvs.
> >
>
> OK, both mails came back, so the limit could have been attained because I
> made a
> lot of chang
l get from cvs.
OK, both mails came back, so the limit could have been attained because I made a
lot of changes previously.
I check anyway on trac that the commit has been correctly pushed in when I do
not get the feedback from cvs, but it is a bit boring that commits come in
without the maint
fr.gmo (however with only 3 changes this time,
instead of ~ a hundred the last time).
We'll see what mails lyx-devel will get from cvs.
--
Jean-Pierre
Am Donnerstag, 9. März 2017 um 18:18:38, schrieb Pavel Sanda
> Richard Heck wrote:
> > >> No. It may be that you are not whitelisted for posting to lyx-cvs.
> > >
> > > There have been posts from j...@lyx.org last month on lyx-cvs.
> >
> > Mystery,
Richard Heck wrote:
> >> No. It may be that you are not whitelisted for posting to lyx-cvs.
> >
> > There have been posts from j...@lyx.org last month on lyx-cvs.
>
> Mystery, then.
IIRC we have some maximal size of mails which can get through our conferences.
Esp
t; 7ca89e49, I did not see an acknowledgement on lyx-devel as usual.
>>> Is this a normal behaviour ?
>>
>> No. It may be that you are not whitelisted for posting to lyx-cvs.
>
> There have been posts from j...@lyx.org last month on lyx-cvs.
Mystery, then.
rh
that you are not whitelisted for posting to lyx-cvs.
There have been posts from j...@lyx.org last month on lyx-cvs.
JMarc
ted for posting to lyx-cvs.
I don't know how to deal with this, but I think JMarc does.
Richard
On Wed, Jun 22, 2016 at 02:16:06PM -0400, Richard Heck wrote:
> On 06/21/2016 07:48 PM, Scott Kostyshak wrote:
> > On Sat, Apr 16, 2016 at 01:43:18PM -0400, Scott Kostyshak wrote:
> >> On Sat, Apr 16, 2016 at 08:35:54AM -0400, Richard Heck wrote:
> >>> On 04/15/2016 05:45 PM, Scott Kostyshak wrote:
On 06/21/2016 07:48 PM, Scott Kostyshak wrote:
> On Sat, Apr 16, 2016 at 01:43:18PM -0400, Scott Kostyshak wrote:
>> On Sat, Apr 16, 2016 at 08:35:54AM -0400, Richard Heck wrote:
>>> On 04/15/2016 05:45 PM, Scott Kostyshak wrote:
On Tue, Mar 29, 2016 at 06:09:56PM -0400, Scott Kostyshak wrote:
On Sat, Apr 16, 2016 at 01:43:18PM -0400, Scott Kostyshak wrote:
> On Sat, Apr 16, 2016 at 08:35:54AM -0400, Richard Heck wrote:
> > On 04/15/2016 05:45 PM, Scott Kostyshak wrote:
> > > On Tue, Mar 29, 2016 at 06:09:56PM -0400, Scott Kostyshak wrote:
> > > > On Tue, Mar 29, 2016 at 10:49:55AM +0200
On Sat, Apr 16, 2016 at 08:35:54AM -0400, Richard Heck wrote:
> On 04/15/2016 05:45 PM, Scott Kostyshak wrote:
> > On Tue, Mar 29, 2016 at 06:09:56PM -0400, Scott Kostyshak wrote:
> > > On Tue, Mar 29, 2016 at 10:49:55AM +0200, Jean-Marc Lasgouttes wrote:
> > > > Le 28/03/2016 00:04, Scott Kostysha
On 04/15/2016 05:45 PM, Scott Kostyshak wrote:
On Tue, Mar 29, 2016 at 06:09:56PM -0400, Scott Kostyshak wrote:
On Tue, Mar 29, 2016 at 10:49:55AM +0200, Jean-Marc Lasgouttes wrote:
Le 28/03/2016 00:04, Scott Kostyshak a écrit :
It seems we currently use "git show ${hash}" in our script. Inste
On Tue, Mar 29, 2016 at 06:09:56PM -0400, Scott Kostyshak wrote:
> On Tue, Mar 29, 2016 at 10:49:55AM +0200, Jean-Marc Lasgouttes wrote:
> > Le 28/03/2016 00:04, Scott Kostyshak a écrit :
> > >It seems we currently use "git show ${hash}" in our script. Instead of
> > >doing two commands like I naiv
On Tue, Mar 29, 2016 at 10:49:55AM +0200, Jean-Marc Lasgouttes wrote:
> Le 28/03/2016 00:04, Scott Kostyshak a écrit :
> >It seems we currently use "git show ${hash}" in our script. Instead of
> >doing two commands like I naively suggested above, what about the
> >following?
>
> What about "git sh
Le 28/03/2016 00:04, Scott Kostyshak a écrit :
It seems we currently use "git show ${hash}" in our script. Instead of
doing two commands like I naively suggested above, what about the
following?
What about "git show --stat"?
JMarc
On Mon, Feb 22, 2016 at 08:52:17PM +0100, Georg Baum wrote:
> Jean-Marc Lasgouttes wrote:
>
> > Le 18/02/2016 02:58, Scott Kostyshak a écrit :
> >> Would anyone else find it useful if the lyx-cvs messages showed the file
> >> names that were changed at the beginnin
Jean-Marc Lasgouttes wrote:
> Le 18/02/2016 02:58, Scott Kostyshak a écrit :
>> Would anyone else find it useful if the lyx-cvs messages showed the file
>> names that were changed at the beginning of a message? One example is
>> that I would often like to know if a commit is
Le 18/02/2016 02:58, Scott Kostyshak a écrit :
Would anyone else find it useful if the lyx-cvs messages showed the file
names that were changed at the beginning of a message? One example is
that I would often like to know if a commit is documentation only or if
there is another change that I
Would anyone else find it useful if the lyx-cvs messages showed the file
names that were changed at the beginning of a message? One example is
that I would often like to know if a commit is documentation only or if
there is another change that I would like to take a look at.
What I would
Neither Guillaume nor I have received emails regarding the last few
commits.
Scott
signature.asc
Description: PGP signature
is in /home/git/repositories/lyx.git/config.
Thanks. It is a bit difficult for me to understand what the code does,
though... Anyway, I propose that lyx-cvs just accepts all messages
coming from lyx.lyx.org. Would that be OK?
I think that would probably be fine, though if there is something
s. It is a bit difficult for me to understand what the code does,
though... Anyway, I propose that lyx-cvs just accepts all messages
coming from lyx.lyx.org. Would that be OK?
JMarc
On 10/19/2015 08:55 AM, Vincent van Ravesteijn wrote:
On Mon, Oct 19, 2015 at 1:38 PM, Jean-Marc Lasgouttes
wrote:
The title says it all. I'd like to add some header in there that the lyx-cvs
list can use to allow the message, instead of restricting to subscribers.
JMarc
It is in a git
On Mon, Oct 19, 2015 at 1:38 PM, Jean-Marc Lasgouttes
wrote:
>
> The title says it all. I'd like to add some header in there that the lyx-cvs
> list can use to allow the message, instead of restricting to subscribers.
>
> JMarc
It is in a git hook in a script called .git/h
The title says it all. I'd like to add some header in there that the
lyx-cvs list can use to allow the message, instead of restricting to
subscribers.
JMarc
ime. I don't know what is wrong with the messages to lyx-cvs-help.
Maybe Jean-Macr can give you the address to contact him directly?
> Currently, all my posts to lyx-cvs-h...@lists.lyx.org as well as
> lyx-cvs-help-milde=users.sf@lists.lyx.org for a help message went
> without
Dear Georg, dear all,
On 2015-09-08, Georg Baum wrote:
> Scott Kostyshak wrote:
>> On Sat, Sep 05, 2015 at 08:42:07AM +, Guenter Milde wrote:
>>> I hope there is a solution that works without me getting all the
>>> auto-generated lyx-cvs posts:
> To my kowl
Scott Kostyshak wrote:
> On Sat, Sep 05, 2015 at 08:42:07AM +, Guenter Milde wrote:
>> I hope there is a solution that works without me getting all the
>> auto-generated lyx-cvs posts:
To my kowledge this is not possible. You need to subscribe with your lyx.org
account.
On Sat, Sep 05, 2015 at 08:42:07AM +, Guenter Milde wrote:
> I hope there is a solution that works without me getting all the
> auto-generated lyx-cvs posts:
Would it be simple to subscribe to lyx-cvs and then just redirect all
messages from lyx-cvs to the trash?
I agree that there sho
Dear Georg and other LyX developers,
> 2) Günters submits do still not show up on the cvs list. Günter, please set
> up your email in such a way that the log messages are accepted by the list.
I tried and thought it should work now.
The email address in my local git repo is set
On Saturday 11 July 2015 23:00:51 Guenter Milde wrote:
> But I do not want to get post from lyx-cvs!
>
> Günter
IIRC you can configure the list to not receive any email, as it is usual for
other lists.
Regards,
--
José Abílio
On 2015-07-11, Richard Heck wrote:
> On 07/11/2015 01:02 PM, Jean-Marc Lasgouttes wrote:
>> Maybe subscribe to thé list with his @lyx.org address ?
> Yes, subscribe to lyx-cvs in particular. Only subscribers can post there.
But I do not want to get post from lyx-cvs!
Günter
On 07/11/2015 01:02 PM, Jean-Marc Lasgouttes wrote:
Maybe subscribe to thé list with his @lyx.org address ?
Yes, subscribe to lyx-cvs in particular. Only subscribers can post there.
rh
Maybe subscribe to thé list with his @lyx.org address ?
JMarc
Le 11 juillet 2015 18:52:56 GMT+02:00, Scott Kostyshak a
écrit :
>He has been using his @lyx.org account. Does anything else need to be
>done?
>
>Scott
He has been using his @lyx.org account. Does anything else need to be done?
Scott
Hi Benjamin,
There are still no mails sent about your commits.
Are you sure you are subscribed to the cvslog mailinglist with your
lyx.org address.
Vincent
On Thu, Mar 13, 2014 at 10:27 AM, Benjamin Piwowarski wrote:
>
> On Thu, Mar 13, 2014 at 10:25 AM, Vincent van Ravesteijn
> wrote:
>>
>> Hi Benjamin,
>>
>> Can you subscribe yourself with the lyx.org e-mail address to
>> lyx-...@lists.lyx.org ? Otherwise, your commit are not sent to this
>> list
Hi Benjamin,
Can you subscribe yourself with the lyx.org e-mail address to
lyx-...@lists.lyx.org ? Otherwise, your commit are not sent to this
list.
Vincent
Am 11.04.2013 um 11:39 schrieb Tommaso Cucinotta :
> On 11/04/13 06:21, Stephan Witt wrote:
>>> Avoid check mistakenly current folder for .git/.svn/.CVS, when going up
>>> the path checking for parents.
>>
>> Why do you think it's a mistake to che
On 11/04/13 06:21, Stephan Witt wrote:
>>Avoid check mistakenly current folder for .git/.svn/.CVS, when going up
>> the path checking for parents.
>
> Why do you think it's a mistake to check the current folder for .git or .svn?
It was checking the current folder fro
7 01:10:31 2013 +0100
>
>Avoid check mistakenly current folder for .git/.svn/.CVS, when going up
> the path checking for parents.
Why do you think it's a mistake to check the current folder for .git or .svn?
Regards,
Stephan
Scott Kostyshak wrote:
> On Sat, Dec 29, 2012 at 11:34 AM, Richard Heck wrote:
>> On 12/29/2012 11:15 AM, Scott Kostyshak wrote:
>>>
>>> On Sat, Dec 29, 2012 at 10:48 AM, Richard Heck wrote:
This can be done. It's a matter of updating the script that sends these
emails. I'll try t
y try to keep up-to-date on pushes to the repo by reading
>>>> the lyx-cvs emails. However, I just realized that I might be missing
>>>> some commits that I would be interested in because when someone pushes
>>>> more than one commit at once, it is stacked in one
On 12/29/2012 11:15 AM, Scott Kostyshak wrote:
On Sat, Dec 29, 2012 at 10:48 AM, Richard Heck wrote:
On 12/28/2012 09:32 PM, Scott Kostyshak wrote:
I currently try to keep up-to-date on pushes to the repo by reading
the lyx-cvs emails. However, I just realized that I might be missing
some
On Sat, Dec 29, 2012 at 10:48 AM, Richard Heck wrote:
> On 12/28/2012 09:32 PM, Scott Kostyshak wrote:
>>
>> I currently try to keep up-to-date on pushes to the repo by reading
>> the lyx-cvs emails. However, I just realized that I might be missing
>> some commits th
On 12/28/2012 09:32 PM, Scott Kostyshak wrote:
I currently try to keep up-to-date on pushes to the repo by reading
the lyx-cvs emails. However, I just realized that I might be missing
some commits that I would be interested in because when someone pushes
more than one commit at once, it is
I currently try to keep up-to-date on pushes to the repo by reading
the lyx-cvs emails. However, I just realized that I might be missing
some commits that I would be interested in because when someone pushes
more than one commit at once, it is stacked in one email. The top one
might be "typos
Georg Baum wrote:
> It was easy to verify that owner_ is always set. I also made it more clear
> that it should never change by making it a const member.
I meant that the buffer to which owner_ points to must remain alive.
Quick peek at Buffer.cpp shows it should be fine during reload.
Pavel
Pavel Sanda wrote:
> Georg Baum wrote:
>> What do you prefer?
>
> No hard opinion, but if you are going to ditch it please make sure
> that owner_ object is living all the time and does not get invalid for
> a critical moment when reloading buffer or so (this kind of robustness
> against changes
Georg Baum wrote:
> What do you prefer?
No hard opinion, but if you are going to ditch it please make sure
that owner_ object is living all the time and does not get invalid for
a critical moment when reloading buffer or so (this kind of robustness
against changes in various bufferReload routines
I am currently cleaning up a patch that implements LFUN_VC_RENAME and
LFUN_VC_COPY for submission. I implemented it originally for my wife in 1.6,
and do not want to port it on each upgrade;-) During the cleanup I stumbled
over the file_ member of the CVS and SVN classes. RCS does not have it
>
>
> Vincent, if it is so important for you to not get big emails, then you
> really have to solve that at your side. Sorting into folders, forwarding
> only small mails, only getting headers etc. You cannot really expect
> people/mailes/svnmailer what ever to solve that for you.
>
No, but one ha
Le 27/05/2011 10:52, Lars Gullik Bjønnes a écrit :
But I can agree that the mails from mailer.py is a bit on the large side
at some times.
Yes, we need something better than mailer.py, but it does not seem
trivial enough to me.
JMarc
Vincent van Ravesteijn writes:
| On Mon, Mar 28, 2011 at 11:25 PM, Jean-Marc Lasgouttes
| wrote:
>
>> Le 28/03/11 19:31, Tommaso Cucinotta a écrit :
>>
>> I can see this was not implemented (see last 2.8MB commit r38082).
>>>
>>> I know there are more important things to think about, however, jus
On Mon, Mar 28, 2011 at 11:25 PM, Jean-Marc Lasgouttes
wrote:
> Le 28/03/11 19:31, Tommaso Cucinotta a écrit :
>
> I can see this was not implemented (see last 2.8MB commit r38082).
>>
>> I know there are more important things to think about, however, just to
>> not
>> forget about this . . . .
>>
Le 17/04/11 23:39, Pavel Sanda a écrit :
This is done now. (easier than pmwiki!)
good news, thanks
For pmwiki I am not even able to understand how the current booki3Ai
password is set. Grep does not turn it up, either in plain text, not in
crypt()ed version. I am not sure what Christian did
Jean-Marc Lasgouttes wrote:
> Le 02/04/11 16:32, Pavel Sanda a écrit :
>> btw could we get updated doxygen documentation on the server?
>> pavel
>
> This is done now. (easier than pmwiki!)
good news, thanks
pavel
Le 02/04/11 16:32, Pavel Sanda a écrit :
btw could we get updated doxygen documentation on the server?
pavel
This is done now. (easier than pmwiki!)
JMarc
Jean-Marc Lasgouttes wrote:
> "apt-get install svnmailer" is rather intimidating. Why would I let it
> install subversion??
my advice was for the case svnmailer is already there and configured.
i wouldn't risk to break svn server by udpating ;)
btw could we get updated doxygen documentation on t
Le 28/03/11 23:30, Pavel Sanda a écrit :
Jean-Marc Lasgouttes wrote:
Le 28/03/11 19:31, Tommaso Cucinotta a écrit :
I can see this was not implemented (see last 2.8MB commit r38082).
I know there are more important things to think about, however, just to
not
forget about this . . . .
I actua
Jean-Marc Lasgouttes wrote:
> Le 28/03/11 19:31, Tommaso Cucinotta a écrit :
>> I can see this was not implemented (see last 2.8MB commit r38082).
>>
>> I know there are more important things to think about, however, just to
>> not
>> forget about this . . . .
>
> I actually looked at it a few day
Le 28/03/11 19:31, Tommaso Cucinotta a écrit :
I can see this was not implemented (see last 2.8MB commit r38082).
I know there are more important things to think about, however, just to not
forget about this . . . .
I actually looked at it a few days ago. It turns out that our mails are
creat
Il 17/02/2011 01:26, Pavel Sanda ha scritto:
Tommaso Cucinotta wrote:
If it is not too difficult, I would propose to cut the attached patches to
a maximum size,
+1
JMarc, this should be just one option in the svn hook scripts.
I can see this was not implemented (see last 2.8MB commit r38082)
Il 17/02/2011 01:22, Tommaso Cucinotta ha scritto:
I'd like to know whether anyone else (apart from myself) has some
troubles with those so long refactoring/new-features patches entirely
sent to the lyx-cvs e-mail box.
just to support the argument: the dictionary e-mail of yesterday
Tommaso Cucinotta wrote:
> If it is not too difficult, I would propose to cut the attached patches to
> a maximum size,
+1
JMarc, this should be just one option in the svn hook scripts.
pavel
Hi all,
I'd like to know whether anyone else (apart from myself) has some
troubles with those so long refactoring/new-features patches entirely
sent to the lyx-cvs e-mail box.
I'm sure I'm using a so bad e-mail client like Thunderbird, however when
opening one of those e-ma
Am 26.10.2010 um 18:19 schrieb Jürgen Spitzmüller:
> Stephan Witt wrote:
>>> I would be more comfortable to wait with this until 1.6.8 is out, so it
>>> can be tested a bit.
>>
>> I'm comfortable with waiting after 1.6.8. We're using 1.6.7 for now.
>> If 1.6.8 is out I can build 1.6.9svn for int
Stephan Witt wrote:
> > I would be more comfortable to wait with this until 1.6.8 is out, so it
> > can be tested a bit.
>
> I'm comfortable with waiting after 1.6.8. We're using 1.6.7 for now.
> If 1.6.8 is out I can build 1.6.9svn for internal use after the patch is
> applied. I'd hope for 1.6.
Am 26.10.2010 um 10:06 schrieb Jürgen Spitzmüller:
> Stephan Witt wrote:
>> The patch is ready and attached.
>> I tested all CVS functions and it works here.
>
> The patch is certainly much bigger than what suits me now, and it introduces
> new strings.
>
> I wou
Stephan Witt wrote:
> The patch is ready and attached.
> I tested all CVS functions and it works here.
The patch is certainly much bigger than what suits me now, and it introduces
new strings.
I would be more comfortable to wait with this until 1.6.8 is out, so it can be
tested a bit.
H
Stephan Witt wrote:
> Now, I have an patch at hand again. I can continue to use and provide a
> patched version
> for my colleges, of course. But I claim it's useful for others, too.
only misunderstanding, i didn't want to dispute backport. i only wanted to have
documentation even in 1.6 so its u
Am 25.10.2010 um 23:14 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> Am 25.10.2010 um 22:01 schrieb Pavel Sanda:
>>
>>> Stephan Witt wrote:
>>>> The patch is ready and attached.
>>>> I tested all CVS functions and it works here.
>>>
&g
Stephan Witt wrote:
> Am 25.10.2010 um 22:01 schrieb Pavel Sanda:
>
> > Stephan Witt wrote:
> >> The patch is ready and attached.
> >> I tested all CVS functions and it works here.
> >
> > looks fine.
>
> Thanks.
>
> > the documentati
Am 25.10.2010 um 22:01 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> The patch is ready and attached.
>> I tested all CVS functions and it works here.
>
> looks fine.
Thanks.
> the documentation of course ;)
Sorry, I don't understand you.
You mean after writi
Stephan Witt wrote:
> The patch is ready and attached.
> I tested all CVS functions and it works here.
looks fine. the documentation of course ;)
pavel
Am 25.10.2010 um 16:53 schrieb Jürgen Spitzmüller:
> Stephan Witt wrote:
>> I'd like to prepare a backport of the CVS backend changes to make it usable
>> in 1.6.8. The dialog part of the changes I would skip so the other
>> backends are not modified.
>> May I do
why on earth there is no mail
anymore from this list to me? It was so before the move from aussie. Did I mis
something?
Kornel
Yes, you have to sign up for the list by sending an empty message to:
lyx-cvs-subscr...@lists.lyx.org <mailto:lyx-cvs-subscr...@lists.lyx.org>
Vincent
Hi,
I commited a version of sk.mo, but now I got a message from
mailer-dae...@wierdlmpc.msci.memphis.edu
about not being able to deliver to :
because of too large message. (> 30 bytes)
Ok, I can understand this.
But, if my commits have made it into this list, why on earth there is n
Christian Ridderström wrote:
> Is the size a problem?
for me no.
> If so, what can I do to avoid it?
in svnmailer.conf i see for_repos and for_paths variables.
pavel
Hi,
When comitting changes to web pages, the attached 'patches' are
unfortunately rather big. I see that the automatically generated posts are
in the order of 40k to 80k sometimes.
Is the size a problem?
If so, what can I do to avoid it?
/Christian
--
Christian Ridderström, +46-8-768 39 44
For information: considering that the messages were just sitting there
using 30M+ of disk space for nothing, I disabled mail delivery of
cvs-log for the mailboxes that are clearly not used. The mails have
been moved to the homedirs of the respective users.
The users concerned are: uwestoehr
I noticed that my 10-part commit of merges to branch didn't generate
massive cvs-log messages. I wonder if it'd be worth setting that value
lower than it is now. Anything over 2---maybe even anything over
1---probably doesn't need to go to the list, I'd guess, as these are
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>> If you look at the archive, you will find that there are not many
>> messages there. Actually, I do not think I am subscribed.
>
> I now understand the correct devel list is lyx-devel@lists.lyx.org and
> is not handled via http://www.lyx.org/mailman
Jean-Marc Lasgouttes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Which one? [EMAIL PROTECTED]
Yes. Is that the wrong list? When I login at this address:
http://www.lyx.org/mailman/listinfo/devel
I see that only Lars and me are subscribed... what a mess.
If you look at the archive,
1 - 100 of 3400 matches
Mail list logo
