Le 31/05/15 16:19, Georg Baum a écrit :
Git has upset me many times as well. The default behaviour is almost always
not what you want, so for the command line version you have to give some
options (which I keep forgetting as well), and I guess this is similar in
the GUI clients you use.
Note th
Uwe Stöhr wrote:
> Yes, that is because of the git mess. I think that I am not too stupid
> but git is nothing for me. Now after years it is still a mystery why
> e.g. often some files are not committed despite I selected them to be
> committed. Also often an older version from my tree is committe
On 05/29/2015 08:29 PM, Uwe Stöhr wrote:
Am 30.05.2015 um 01:17 schrieb Scott Kostyshak:
I agree that this is indeed a good goal. But I find that you often
have follow-up commits.
Yes, that is because of the git mess. I think that I am not too stupid
but git is nothing for me. Now after year
On 05/29/2015 07:17 PM, Scott Kostyshak wrote:
On Thu, May 28, 2015 at 6:47 PM, Uwe Stöhr wrote:
Am 26.05.2015 um 04:00 schrieb Scott Kostyshak:
Nevertheless my aim was to split the commits into small
pieces that can easily be reverted if necessary.
I agree that this is indeed a good goal. But
Am 30.05.2015 um 01:17 schrieb Scott Kostyshak:
I agree that this is indeed a good goal. But I find that you often
have follow-up commits.
Yes, that is because of the git mess. I think that I am not too stupid
but git is nothing for me. Now after years it is still a mystery why
e.g. often so
Am 29.05.2015 um 05:59 schrieb Stephan Witt:
I can recommend the tool SourceTree from Atlassian.
It's available on Windows and Mac. (Yes, no Linux version.)
Thanks. I just downloaded it and will give it a try.
regards Uwe
On Thu, May 28, 2015 at 6:47 PM, Uwe Stöhr wrote:
> Am 26.05.2015 um 04:00 schrieb Scott Kostyshak:
> Nevertheless my aim was to split the commits into small
> pieces that can easily be reverted if necessary.
I agree that this is indeed a good goal. But I find that you often
have follow-up commi
Am Freitag, 29. Mai 2015 um 05:59:48, schrieb Stephan Witt
> Am 29.05.2015 um 00:47 schrieb Uwe Stöhr :
>
> > Am 26.05.2015 um 04:00 schrieb Scott Kostyshak:
> >
> >>> I did not update all references. Work was in progress. Now everything
> >>> should
> >>> work.
> >>
> >> My personal opinion i
Am 29.05.2015 um 00:47 schrieb Uwe Stöhr :
> Am 26.05.2015 um 04:00 schrieb Scott Kostyshak:
>
>>> I did not update all references. Work was in progress. Now everything should
>>> work.
>>
>> My personal opinion is the following: try your best to not commit work
>> in progress. If you would like
Am 26.05.2015 um 04:00 schrieb Scott Kostyshak:
I did not update all references. Work was in progress. Now everything should
work.
My personal opinion is the following: try your best to not commit work
in progress. If you would like to commit work on progress, do not do
it on master. Create a
On 05/27/2015 10:56 AM, Georg Baum wrote:
Scott Kostyshak wrote:
On Mon, May 25, 2015 at 7:24 PM, Uwe Stöhr wrote:
I did not update all references. Work was in progress. Now everything
should work.
My personal opinion is the following: try your best to not commit work
in progress. If you wou
Scott Kostyshak wrote:
> On Mon, May 25, 2015 at 7:24 PM, Uwe Stöhr wrote:
>> Am 24.05.2015 um 20:01 schrieb Kornel Benko:
>>
>>> It seems like tex2lyx from input like
>>> \include{\string"Dummy Document\string".tex}
>>> creates a lyx file which contains
>>> filename "DummyDocumen
On Mon, May 25, 2015 at 7:24 PM, Uwe Stöhr wrote:
> Am 24.05.2015 um 20:01 schrieb Kornel Benko:
>
>> It seems like tex2lyx from input like
>> \include{\string"Dummy Document\string".tex}
>> creates a lyx file which contains
>> filename "DummyDocument.lyx.lyx"
>>
>> This looks wron
Am 24.05.2015 um 20:01 schrieb Kornel Benko:
It seems like tex2lyx from input like
\include{\string"Dummy Document\string".tex}
creates a lyx file which contains
filename "DummyDocument.lyx.lyx"
This looks wrong, I would expect
filename "DummyDocument.lyx"
I did not up
Uwe Stöhr wrote:
> Nevertheless I knew that I will add example by examply to the TeX file
> and therefore did not update the reference at every step.
As I explained in my other message updating them step by step is important,
so please do this in the future.
> However, now everything should be
Uwe Stöhr wrote:
> Am 19.05.2015 um 21:20 schrieb Georg Baum:
>
>> unfortunately the tex2lyx test failures increased (see attachment). Are
>> you aware that this wastes time of developers? Did you see the questions
>> Scott ansd I asked about the failing tests?
>
> Hi Georg,
>
> no because I co
Am Donnerstag, 21. Mai 2015 um 02:50:23, schrieb Uwe Stöhr
> Am 20.05.2015 um 14:44 schrieb Kornel Benko:
>
> > But you do it already, calling 'development/cmake/build.bat' for instance.
>
> Yes, I do.
>
> > What is so difficult to add some line as 'ctest someting' in a script?
>
> Well the "s
Am 20.05.2015 um 14:44 schrieb Kornel Benko:
But you do it already, calling 'development/cmake/build.bat' for instance.
Yes, I do.
What is so difficult to add some line as 'ctest someting' in a script?
Well the "something" is exactly the problem. What should I add there and
what does ctes
Am 20.05.2015 um 11:49 schrieb Vincent van Ravesteijn:
That's the problem. The thing to be tested is not whether LyX can
import without errors, but it is that the resultant LyX file is
_identical_ to the LyX file that is in the repository.
If you add extra test cases in the tex file, you should
Am Mittwoch, 20. Mai 2015 um 00:24:58, schrieb Uwe Stöhr
> Could you please tell me how I could run the test automatically.
> Fiddling around with the command line is very annoying.
But you do it already, calling 'development/cmake/build.bat' for instance.
What is so difficult to add some line a
On Wed, May 20, 2015 at 12:24 AM, Uwe Stöhr wrote:
> Am 19.05.2015 um 21:20 schrieb Georg Baum:
>
>> unfortunately the tex2lyx test failures increased (see attachment). Are
>> you
>> aware that this wastes time of developers? Did you see the questions Scott
>> ansd I asked about the failing tests?
Am 19.05.2015 um 21:20 schrieb Georg Baum:
unfortunately the tex2lyx test failures increased (see attachment). Are you
aware that this wastes time of developers? Did you see the questions Scott
ansd I asked about the failing tests?
Hi Georg,
no because I could access the mailing list until no
22 matches
Mail list logo
