Hello Mark, Tuesday, October 17, 2017, 9:59:01 PM, Mark wrote:
>> Currently, with the CVS and SVN clients I use - necessarily on >> Windows, since our doc app is Windows-based - I can commit, check out, >> etc. from a right click on the /manual/ subdir, or any subdir beneath >> it. Given that I'm committing to multiple projects, this is a >> blessing that I will miss badly. > You can use a subversion client if you want: GitHub provides a > compatibility layer that will make a git repository accessible as if it > is a subversion repository. The only reason to entertain the idea of using SVN would be if the CVS repository were converted to SVN and retained on SF. Since everything is moving towards a Git repository on GitHub, there's no reason to put SVN in the picture at all. >> After all these months with the core project on GitHub, I have yet to >> succeed in downloading the repository AT ALL to access the readme >> files in the core tree for use in the release notes. I have to rely >> on Dmitry sending me a link, from which I can view a file and >> copy/paste it into my local resource directory for that version. > That sounds problematic. Could you send me a private email with the > problems you run into? >From my dabblings with your test project yesterday, I think my problems are with the Git desktop, mostly. I don't like the UI much at all, although being able to connect from it to the source project is a nice feature, but not a life saver. When I get clear of the current crop of alligators, I'll download the Tortoise client app as the TortoiseCVS and SVN packages always served me adequately. > You will not need to checkout the Firebird sources to work with the > documentation: they will be separate, individual, repositories, instead > of one big repository with 'modules'. OK, I'll take your word for it. ;-) Once I get an initial setup, I think I'll be good to go. But I strongly doubt I'll have the time for deep study this week or next. > And as to working like you currently do: you could still do it that way, > but using git to its fullest might make things easier after the initial > learning curve. I agree; thanks to your demo, I'm comfortable that I will be able to sync with the source repo without the whitespace and line-ending problem. I think getting the way updates and commits work will come when I'm not under as much stress as Firebird issues are giving me right now. As for the images for the Developer's Guide, the Ringlish text I'm editing is in Word and the screenshots are (probably) .wmf. But, as the screenshots are all in Russian/Cyrillic, someone with Visual Studio is going to have to re-shoot them from an English language environment, anyway. AFAIR, images we have used in the past have been .png, but Paul V. might have some preference, anyway. Helen ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
