On 13/03/2012 8:13 PM, Lars Gullik Bjønnes wrote:
But why?
This is the perfect case for a separate repo.
> [...]
>
| Assuming that the pristinity of the lyx repo as a whole is so
| important that we cannot allow trusted developers to create branches,
| then maybe such branches can be allowed
Tommaso Cucinotta writes:
| Il 13/03/2012 23:18, Jean-Marc Lasgouttes ha scritto:
>> Can we get to see the diff as in the good old days?
>
| does it depend on me ? or, somebody needs to set-up something
| somewhere :-) ?
>
| Once the diff-to-email will be set-up, will we see all the pushed
| comm
Julien Rioux writes:
| On 13/03/2012 5:58 PM, Lars Gullik Bjønnes wrote:
>> Julien Rioux writes:
>>
>> | it should be allowed to have feature branches
>> | directly in the main repo.
>>
>> This is the part that I really disagree with. Plainly: no, you should
>> not be allow to create what ever b
Jean-Marc Lasgouttes writes:
| Le 14/03/12 00:07, tomm...@lyx.org a écrit :
>> Author: Tommaso Cucinotta
>> Date: Tue, 13 Mar 2012 23:05:36 +
>> New Commit: 5ac1f9400f942e8c73927d6a8a68b3c64b6fa5b8
>> URL:
>> http://git.lyx.org/?p=lyx.git;a=commit;h=5ac1f9400f942e8c73927d6a8a68b3c64b6fa5b8
>
Il 13/03/2012 23:18, Jean-Marc Lasgouttes ha scritto:
Can we get to see the diff as in the good old days?
does it depend on me ? or, somebody needs to set-up something somewhere
:-) ?
Once the diff-to-email will be set-up, will we see all the pushed
commits to all the branches/repos on git.
On 13/03/2012 5:58 PM, Lars Gullik Bjønnes wrote:
Julien Rioux writes:
| it should be allowed to have feature branches
| directly in the main repo.
This is the part that I really disagree with. Plainly: no, you should
not be allow to create what ever branch you want in the main repo.
Please
Le 14/03/12 00:07, tomm...@lyx.org a écrit :
Author: Tommaso Cucinotta
Date: Tue, 13 Mar 2012 23:05:36 +
New Commit: 5ac1f9400f942e8c73927d6a8a68b3c64b6fa5b8
URL:
http://git.lyx.org/?p=lyx.git;a=commit;h=5ac1f9400f942e8c73927d6a8a68b3c64b6fa5b8
Log:
Advertising change as in commit c324d6eae
Le 13/03/12 21:33, Georg Baum a écrit :
We are talking about the _stable_ branch, and I simply don't like to
announce support of a new feature there if it is already known that the
implementation has a principal problem. Currently, the man page tells that
verbatim is not supported. The current im
On 03/13/2012 06:24 PM, Lars Gullik Bjønnes wrote:
Tommaso Cucinotta writes:
| Il 13/03/2012 22:04, Richard Heck ha scritto:
| Should I clone with
| |git clone g...@git.lyx.org:lyx
this one.
But you will have to send me your public ssh key first.
And in case it's not clear: Once that is se
Tommaso Cucinotta writes:
| Il 13/03/2012 22:04, Richard Heck ha scritto:
>> On 03/13/2012 05:56 PM, Tommaso Cucinotta wrote:
>>> Did we make the definitive with no-return move to git ?
>>>
>> Yes. For some info, which is still in process, see
>> http://wiki.lyx.org/Devel/LyXGit.
>
| Should I clo
Pavel Sanda writes:
| Pavel
| BTW Lars, can we get wiki and web working again? Christian stop to
| respond altogether..
I was really hoping that I should not have to look at this, this is
something that I really have not playing with before.
I'll handle apache config, deamons, distributions, git
Il 13/03/2012 22:04, Richard Heck ha scritto:
On 03/13/2012 05:56 PM, Tommaso Cucinotta wrote:
Did we make the definitive with no-return move to git ?
Yes. For some info, which is still in process, see
http://wiki.lyx.org/Devel/LyXGit.
Should I clone with
|git clone g...@git.lyx.org:lyx
or
Richard Heck writes:
| (i) I have forked the main repo on the server to create
| developers/rgheck/lyx. How do I enable read access for the web site,
| and for other developers?
I thought that I mentionded this in "ssh g...@git.lyx.org help"?
No not in clear text it seems. It is the "setperms" m
On 03/13/2012 05:56 PM, Tommaso Cucinotta wrote:
Did we make the definitive with no-return move to git ?
Yes. For some info, which is still in process, see
http://wiki.lyx.org/Devel/LyXGit.
Richard
Julien Rioux writes:
| it should be allowed to have feature branches
| directly in the main repo.
This is the part that I really disagree with. Plainly: no, you should
not be allow to create what ever branch you want in the main repo.
This is the repo with the higher goals and that everyone els
Did we make the definitive with no-return move to git ?
$ svn commit
Trasmissione dati .svn: Commit fallito (seguono dettagli):
svn: Access denied
or, is there any other sort of problem with the server ?
Thanks,
T.
Vincent van Ravesteijn writes:
>> | After that I will gradually make the new repo more and more accessiable:
>> | -> add to gitweb
>>
>> added, viewable at http://git.lyx.org/
>>
>> | -> add to daemon (enable + add)
>>
>> added, anon access to close with
>>
>> git clone git://git.lyx.org/lyx
>>
Uwe Stöhr wrote:
> Am 10.03.2012 13:53, schrieb Georg Baum:
>
>> Yes. Unfortunately this is not done, since special properties of
>> characters like % are already handled in the tokenize phase. For example,
>>
>> \begin{verbatim}
>> x
>> %\end{verbatim}
>>
>> is not handled correctly, since tex2l
On 14/03/2012 7:45 a.m., Julien Rioux wrote:
On 07/03/2012 3:00 AM, Jean-Marc Lasgouttes wrote:
Le 07/03/2012 05:04, Andrew Parsloe a écrit :
(Most of my posts should really go to a tinkerers' list --
lyx-tin...@lists.org? -- for matters lying between the developers' list
and the users' list.
Uwe Stöhr wrote:
> Am 10.03.2012 13:54, schrieb Georg Baum:
>
>> I would not put it in branch right now (see my other mail for details). I
>> would rather like to see a better aproach (reading with changed catcodes
>> or character by character) mature a bit in trunk before it is backported.
>
>
Julien Rioux wrote:
> Down the road, it would be nice to detect the citation engine by using
> whatever trick is used right now to detect that a specific \usepackage
> line should add a specific module, instead of hardcoding a list of
> modules. I don't know enough about this to do it just yet, bu
Here's what I did:
./autogen.sh
mkdir build-devel
cd build-devel
../configure --with-version-suffix=-devel
make
After this I get a lot of changes to po files and also gmo files created
in the src tree. I would have expected that any files that need to be
regenerated would have been created in
Kornel Benko wrote:
> My mistake (bad question). I wanted to know why 755 is needed for the .py
> files, since we are calling them explicitly with python. Nonetheless I
> changed it for cmake too.
If somebody wants to call them in his own script. I also believe that some
linux distros have polic
Jürgen Spitzmüller wrote:
> Georg Baum wrote:
>> > Or better we add another flag "notermination" for commands that do not
>> > need to be terminated.
>>
>> Sounds good. Another benefit: It would also allow to keep the logic in
>> tex2lyx and lyx automatically synchronized.
>
> I'll commit the pa
So here are some questions from me about how to get started using git,
as opposed to git-svn. All of this has to do with server side stuff, I
guess.
I now have two local repos: lyx-devel and lyx-20, for trunk and branch.
In each one, I have several local branches of my own, e.g.:
../lyx/ly
Julien Rioux wrote:
> On 10/03/2012 8:20 AM, Georg Baum wrote:
>> The roundtrip output of one of the tex2lyx tests has changed recently:
>>
>> tex2lyx -roundtrip src/tex2lyx/test/test-insets.tex
>>
>> will produce src/tex2lyx/test/test-insets.lyx.lyx and
>> src/tex2lyx/test/test- insets.lyx.tex. I
Pavel Sanda wrote:
> From what I see there are roughly 3 kinds of things committed into trunk
> as far as time and testing is concerned
>
> 1. Short-time one shots, e.g. fixing small glitches, doc changes,
> translations.
>Sometimes can take few minutes to produce and once committed there is
On 13/03/2012 11:39 AM, Pavel Sanda wrote:
Lars Gullik Bj?nnes wrote:
You, the lyx developers, have to agree on process, but the git repo
has been open for writing since sunday evening.
From what I see there are roughly 3 kinds of things committed into trunk
as far as time and testing is conc
On 06/03/2012 5:41 PM, Andrew Parsloe wrote:
[...] export this as plain text. When viewed in a text editor, it looks like:
First line.
Second line.
Third line.
which seems wrong to me. If I had exported to LaTeX or TeX then the
blank lines would correctly mark the ends of paragraphs, but in a
On 07/03/2012 3:00 AM, Jean-Marc Lasgouttes wrote:
Le 07/03/2012 05:04, Andrew Parsloe a écrit :
(Most of my posts should really go to a tinkerers' list --
lyx-tin...@lists.org? -- for matters lying between the developers' list
and the users' list.)
When I reconfigure LyX and then look at the c
On 11/03/2012 2:57 PM, Niklas Burtscheid wrote:
Wasn't that here a bug-report?
Original-Nachricht
Datum: Tue, 06 Mar 2012 00:58:46 +0100
Von: "Uwe Stöhr"
An: Niklas Burtscheid
CC: lyx-devel@lists.lyx.org
Betreff: Re: Bug: Temporary directory can\'t be deleted
Am 04.03.2012
On 03/13/2012 12:12 PM, Vincent van Ravesteijn wrote:
Op 13-3-2012 16:47, Richard Heck schreef:
On 03/13/2012 08:40 AM, Vincent van Ravesteijn wrote:
You, the lyx developers, have to agree on process, but the git
repo has been open for writing since sunday evening.
I propose the following:
Op 13-3-2012 16:47, Richard Heck schreef:
On 03/13/2012 08:40 AM, Vincent van Ravesteijn wrote:
You, the lyx developers, have to agree on process, but the git repo
has been open for writing since sunday evening.
I propose the following:
I don't disagree with any of what is below, but I guess
I see that in some cases of 2. additional commit are applied but we shouldn't
value clean commit history at such high rates.
These additional commits are the number 1 reason for me to propose what
I proposed. To my liking, there are way too many commits that fix a
typo, fix a warning on a diff
On 03/13/2012 08:40 AM, Vincent van Ravesteijn wrote:
You, the lyx developers, have to agree on process, but the git repo
has been open for writing since sunday evening.
I propose the following:
I don't disagree with any of what is below, but I guess I'd prefer to
see us move more slowly. Ma
Lars Gullik Bj?nnes wrote:
> You, the lyx developers, have to agree on process, but the git repo
> has been open for writing since sunday evening.
>From what I see there are roughly 3 kinds of things committed into trunk
as far as time and testing is concerned
1. Short-time one shots, e.g. fixing
| After that I will gradually make the new repo more and more accessiable:
| -> add to gitweb
added, viewable at http://git.lyx.org/
| -> add to daemon (enable + add)
added, anon access to close with
git clone git://git.lyx.org/lyx
is now enabled.
How can I assign rewrite or forced update
You, the lyx developers, have to agree on process, but the git repo
has been open for writing since sunday evening.
I propose the following:
Goal:
Do not merge any new features into lyx.git until
- they are truly finished,
- well commented and understandable by others,
- have good commit mess
Uwe Stöhr writes:
| Am 12.03.2012 23:07, schrieb Uwe Stöhr:
>
>> The attached patch implements this. This would be a fileformat change. OK?
>> (the necessary tex2lyx change follows)
>
| Now the tex2lyx part is included.
>
| tex2lyx btw. never supported rotated table cells and has a bug (#8081).
First, you have to do
git checkout 2.0.x
This will create the branch from the upstream branch.
Vincent
Op 13 mrt. 2012 07:26 schreef "Stephan Witt" het volgende:
>
> Am 12.03.2012 um 19:56 schrieb Vincent van Ravesteijn:
>
> > Op 11-3-2012 22:43, Richard Heck schreef:
> >> On 03/11/2012 05:37
40 matches
Mail list logo
