Hi Mark,
my Github username is MartinKoeditz.
Regards,
Martin
-Ursprüngliche Nachricht-
Von: Paul Vinkenoog [mailto:p...@vinkenoog.nl]
Gesendet: Montag, 6. November 2017 03:28
An: Chatter regarding Firebird documentation
Betreff: Re: [Firebird-docs] Test repository CVS to git
On 5-11-2017 19:27, Helen Borrie wrote:
Sunday, November 5, 2017, 1:42:35 AM, Mark wrote:
So what are the next steps?
I'm waiting on Helen to give the final go.
Actually, I was waiting to see some comment from Paul V.
As Paul has given his OK too, I will perform the migration next weeken
Helen wrote:
>> I'm waiting on Helen to give the final go.
>
> Actually, I was waiting to see some comment from Paul V.
And I was waiting for yours, since you were the only one with
potential issues regarding Git :-)
Anyway, since you seem to be confident it will work for you now,
I'm neutral an
Sunday, November 5, 2017, 1:42:35 AM, Mark wrote:
>>> So what are the next steps?
> I'm waiting on Helen to give the final go.
Actually, I was waiting to see some comment from Paul V.
I still seem to have one or two novice issues on this side but they
are not showstoppers. Over the weekend I c
Hi Mark,
On 04/11/17 12:42, Mark Rotteveel wrote:
And although it is not an impediment for the migration itself, it would
be handy to have a list of the GitHub usernames of contributors that
need commit access to the repository.
Mine is "NormanDunbar" - if you want it now that is!
Alternati
On 2-11-2017 10:27, Köditz, Martin wrote:
Hello everybody,
I’ve worked with Mark’s Git repo for a while. I haven’t found any
problems yet. So I think we should really migrate.
I had a few requests regarding the move. More translators want to
collaborate based on the Git environment. So far,
Hello everybody,
I've worked with Mark's Git repo for a while. I haven't found any problems yet.
So I think we should really migrate.
I had a few requests regarding the move. More translators want to collaborate
based on the Git environment. So far, I had to put these off. It would be nice
to
Helen Borrie wrote:
I just did an actual clone of the test#4 repository and the Readme
looks just as it ought to. I'm also abandoning the GitHub Desktop in
favour of TortoiseGit. It feels familiar, even if I don't understand
most of the lingo. I'll try to grokk that over the weekend, at least
Friday, October 20, 2017, 7:22:25 AM, you wrote:
> Thursday, October 19, 2017, 9:07:39 PM, Mark wrote:
>> The line-endings of ReadMe are correct in my checkout, which means the
>> git autodetection is working for me. I could add ReadMe explicitly in
>> .gitattributes, but that shouldn't make a d
Thursday, October 19, 2017, 9:07:39 PM, Mark wrote:
> The line-endings of ReadMe are correct in my checkout, which means the
> git autodetection is working for me. I could add ReadMe explicitly in
> .gitattributes, but that shouldn't make a difference (it should already
> be caught by "* text=aut
On 2017-10-18 19:52, Helen Borrie wrote:
Thursday, October 19, 2017, 4:11:59 AM, Mark wrote:
So if a new file extension for a text file would be introduced between
now and the final conversion, then I would specifically need to take
that into account, or we'll get a white space correction on th
Thursday, October 19, 2017, 4:11:59 AM, Mark wrote:
> So if a new file extension for a text file would be introduced between
> now and the final conversion, then I would specifically need to take
> that into account, or we'll get a white space correction on the first
> commit that touches that f
On 2017-10-18 16:45, Norman Dunbar wrote:
On 18/10/17 15:15, Mark Rotteveel wrote:
Given the normalization done during conversion, that should not be a
problem (unless a new file extension is introduced that isn't
considered a text file by the configuration of the conversion).
The thing I me
On 18/10/17 15:15, Mark Rotteveel wrote:
Given the normalization done during conversion, that should not be a
problem (unless a new file extension is introduced that isn't considered
a text file by the configuration of the conversion).
The thing I mentioned with autocrlf is the old way of doi
On 2017-10-18 15:35, Norman Dunbar wrote:
Afternoon Paul,
On 18/10/17 14:08, Paul Vinkenoog wrote:
A number of source files in my (Windows) CVS working dir have Unix
line endings though, whereas their Git counterparts have DOS endings.
That's no problem, as long as it doesn't lead to a huge
On 2017-10-18 15:08, Paul Vinkenoog wrote:
Mark Rotteveel wrote:
Fixed in https://github.com/mrotteveel/test-firebird-documentation-4
I cloned this repository and built a number of targets, both in master
and in the B_Release branch.
Everything worked exactly as in my CVS checkout.
A number
Hi Norman,
>> A number of source files in my (Windows) CVS working dir have Unix line
>> endings though, whereas their Git counterparts have DOS endings.
>>
>> That's no problem, as long as it doesn't lead to a huge number of 'changes'
>> and log messages when such a file is committed, clutterin
Afternoon Paul,
On 18/10/17 14:08, Paul Vinkenoog wrote:
A number of source files in my (Windows) CVS working dir have Unix line endings
though, whereas their Git counterparts have DOS endings.
That's no problem, as long as it doesn't lead to a huge number of 'changes' and
log messages when
Mark Rotteveel wrote:
> Fixed in https://github.com/mrotteveel/test-firebird-documentation-4
I cloned this repository and built a number of targets, both in master and in
the B_Release branch.
Everything worked exactly as in my CVS checkout.
A number of source files in my (Windows) CVS working
Hi Mark,
I used your repository for few Tests and further translation. I couldn't find
any problems. The Linux scripts are working and no strange behavior when I
create the html or pdf outputs.
>From my point of view everything is fine and it is much easier to add new
>contents (for me).
Rega
> > https://link.springer.com/book/10.1007%2F978-1-4842-0076-6
> Thanks Paul, but I was referring to the fact that I had, in the past,
> downloaded the book from the https://git-scm.com/book/en/v2 address. :-)
>
> I already have it from the Springer address too, so I have both versions.
I ju
On 17/10/17 14:41, Paul Beach wrote:
I'm sure I've
downloaded the PDF from there in the past. (Must check!)
https://link.springer.com/book/10.1007%2F978-1-4842-0076-6
Regards
Paul
Thanks Paul, but I was referring to the fact that I had, in the past,
downloaded the book from the https://gi
On 17-10-2017 08:12, Köditz, Martin wrote:
Hi,
seems I got unsubscribed from the list. So I had some trouble to be part
of the discussion. I will try it again.
Do we have any problems with special characters? Please have a look at
https://github.com/mrotteveel/test-firebird-documentation-3/t
> I'm sure I've
> downloaded the PDF from there in the past. (Must check!)
https://link.springer.com/book/10.1007%2F978-1-4842-0076-6
Regards
Paul
--
Check out the vibrant tech community on one of the world's most
engag
If anyone is interested, Pro Git (Second Edition) by Scott Chacon and
Ben Straub is officially available as PDF or EPUB from Springer's Web
Site at https://www.springer.com/gb/book/9781484200773 - I believe that
Springer are associated with Apress who publish the book.
The book is also availab
On 17-10-2017 11:15, Mark Rotteveel wrote:
I'm sure that's not how it's done but at least I am comfortable with
the migrated file formats and filesystem structure, so far. It looks
possible that I will be able to sync the working source files with the
git ones, much as I was doing with CVS and S
On 17-10-2017 06:44, Helen Borrie wrote:
I downloaded the zip from your repository and looked at a few of the
.docbook files from the v.3.0.2 release notes with the editor I use
for creating and updating them. They look OK to me.
The ReadMe file in the base directory has messed-up line-ending
On 17-10-2017 08:12, Köditz, Martin wrote:
Hi,
seems I got unsubscribed from the list. So I had some trouble to be part
of the discussion. I will try it again.
Do we have any problems with special characters? Please have a look at
https://github.com/mrotteveel/test-firebird-documentation-3/t
Hi,
seems I got unsubscribed from the list. So I had some trouble to be part of the
discussion. I will try it again.
Do we have any problems with special characters? Please have a look at
https://github.com/mrotteveel/test-firebird-documentation-3/tree/master/src/docs/refdocs-de/langref/fblangr
Hello Mark,
Monday, October 16, 2017, 3:41:43 AM, you wrote:
> I have made a few more test runs, the end result is in
> https://github.com/mrotteveel/test-firebird-documentation-3
> I think this would be the final run.
> Difference against yesterday:
> - Removed the d_jencks branch
> - Added
Hi Mark,
> I have made a few more test runs, the end result is in
> https://github.com/mrotteveel/test-firebird-documentation-3
>
> I think this would be the final run.
>
> Difference against yesterday:
>
> - Removed the d_jencks branch
> - Added a .gitignore to ignore build files
> - Added a
I have made a few more test runs, the end result is in
https://github.com/mrotteveel/test-firebird-documentation-3
I think this would be the final run.
Difference against yesterday:
- Removed the d_jencks branch
- Added a .gitignore to ignore build files
- Added a .gitattributes with sane defa
32 matches
Mail list logo
