Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th
On 18/10/17 02:40, Helen Borrie wrote: >>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. Where I'm having to work with projects that perhaps jumped to git too soon, I'm using TortoiseHg with git-hg. It provides views and navigation tools that I've been used to and gives a common base for CVS and SVN as well as GIT and the native HG which I've been using locally as an alternative to GIT. I don't know about the current GIT UI tools but it was simply not cross platform and complete at the time I was having to live with the change ... In my book GIT may have filled holes in CVS operations, but it also lost key facilities CVS was good at. The resulting project ports are now difficult to work with as a whole where one has dozens of isolated module which on CVS one could create a single view of selected 'sub-repos' :( -- Lester Caine - G8HFL - Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- 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
Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th
Helen Borrie 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. For Windows, I'd recommend TortoiseGit: https://tortoisegit.org/ It's a GUI for Git that's implemented as a Windows Explorer integration, and you do commits and push/pull from the right-click menu. Very much like TortoiseSVN. Regards, Kjell Rilbe Telefon: 08-761 06 55 Mobil: 0733-44 24 64 Marknadsinformation i Sverige AB Ulvsundavägen 106C 168 67 Bromma www.marknadsinformation.se 08-514 905 90 -- 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
Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th
On 16-10-2017 22:58, Helen Borrie wrote: I guess I have to say (to quote my ex-Navy husband) "that's life in a blue suit." My preference would have been to convert to SVN and leave the repository on Sourceforge - don't fix what aint broke. But Github seems to dominate our (project) lives these days. 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. 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? As for code control, I currently keep two copies of the /manual/ branch: one for working on and the other which I sync with the working one before committing. I have no idea how I will manage with the Github thing. Any docs I have read so far (and I have not tried in recent months) assumes that one is working on the entire source code tree. I do NOT want to keep a current copy of the entire tree. To consult core source code, it is simple for me to find what I want in the repository and copy/paste it, since I never commit changes to that code. 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'. 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. In git you can make local branches, commit changes to that local branch, and you can easily switch between the master branch and that local branch. Once you are happy with that, you can merge that local branch back to master with the commits you made on the local branch and 'push' that to the repository on GitHub. You could 'squash' the changes in the local branch to a single commit on master (but that is a bit more 'advanced' git). On the other hand, for Jaybird I use separate local copies for Jaybird 4 (master branch), Jaybird 3 (Branch_3_0) and Jaybird 2.2 (Branch_2_2), because that is simpler with uncommitted changes in progress. I guess I just have to work something out. This is about the worst week Mark could have picked, from my POV, as I'm already burning the midnight oil on other project infrastructure problems and TRYING (in conjunction with Denis Simonov) to sort out the Ringlish translation of the FB Developer's Guide. The fact that I did the test conversion this weekend does not put a rush on you. We have until the 30th of November before we lose write access to the CVS repository, moving before that time would probably be better, but we can still move after that time if that is better for your schedule. However it would be great if there are more eyes on the conversion than just me. For example with the test conversion of OdbcJdbc, Alexander already found a conversion issue that I hadn't detected because he used the GitHub subversion support, and the git client automatically 'fixed' the issue. If necessary I can also grant write access to the test repository. Note that Denis will have to be "in" on any changes as, this time around, he is planning to convert the Word text to DocBook himself and (presumably) commit the DocBook source once he has built it successfully. Amongst other things, he has quite a number of screenshots there which, of course, are binary files. I have no idea how GH deals with image files but I guess we are going to find out soon enough. I can't walk him through it myself, since I am clueless about how it's going to work. Git by default uses a few heuristics to determine if a file is binary or not, and you can override that by explicitly setting the behavior for a file pattern in the .gitattributes file, like I did for the test conversion (see https://github.com/mrotteveel/test-firebird-documentation-3/blob/master/.gitattributes ). I already added the most likely image types to that file. Adding new types is just a matter of editing that file. Mark -- Mark Rotteveel -- 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
Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th
Thursday, October 12, 2017, 12:59:11 AM, Paul V. wrote: > Hi all, > Three people - one of them a committer - have expressed their preference > for moving to GitHub. > I have no problem with that, but I would also like to hear Helen's opinion, > as she is the heaviest user of the manual module. I guess I have to say (to quote my ex-Navy husband) "that's life in a blue suit." My preference would have been to convert to SVN and leave the repository on Sourceforge - don't fix what aint broke. But Github seems to dominate our (project) lives these days. 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. 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. As for code control, I currently keep two copies of the /manual/ branch: one for working on and the other which I sync with the working one before committing. I have no idea how I will manage with the Github thing. Any docs I have read so far (and I have not tried in recent months) assumes that one is working on the entire source code tree. I do NOT want to keep a current copy of the entire tree. To consult core source code, it is simple for me to find what I want in the repository and copy/paste it, since I never commit changes to that code. I guess I just have to work something out. This is about the worst week Mark could have picked, from my POV, as I'm already burning the midnight oil on other project infrastructure problems and TRYING (in conjunction with Denis Simonov) to sort out the Ringlish translation of the FB Developer's Guide. Note that Denis will have to be "in" on any changes as, this time around, he is planning to convert the Word text to DocBook himself and (presumably) commit the DocBook source once he has built it successfully. Amongst other things, he has quite a number of screenshots there which, of course, are binary files. I have no idea how GH deals with image files but I guess we are going to find out soon enough. I can't walk him through it myself, since I am clueless about how it's going to work. 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
Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th
On 11-10-2017 13:59, Paul Vinkenoog wrote: Hi all, Three people - one of them a committer - have expressed their preference for moving to GitHub. Two committers, although it has been a while (3 years AFAICT), I have committed to the manual module. I have no problem with that, but I would also like to hear Helen's opinion, as she is the heaviest user of the manual module. Sure, I will just do a test conversion for now to work out the kinks (if any), and document the necessary steps. Mark -- Mark Rotteveel -- 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
Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th
Mark Rotteveel wrote: >> I am willing to spend some time to test and perform the conversion of >> the manual module to Git (and GitHub), so the commit history is >> preserved. If the consensus is for subversion, I can do that as well. > > I'll be doing a test conversion of the ODBC repository this weekend. If > it is quick to do, I'll also do a test conversion of the docs repository. Thanks, that would be most interesting. I'm especially curious about the preservation of the history, including branches (not that we have many of those). Cheers, Paul Vinkenoog -- 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
Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th
On 9-10-2017 09:13, Mark Rotteveel wrote: I think it would be preferable if the documentation project would move to GitHub (https://github.com/FirebirdSQL), where the main project resides. If complexity of git is a problem: GitHub also allows subversion access to a git repository: https://help.github.com/articles/support-for-subversion-clients/ I am willing to spend some time to test and perform the conversion of the manual module to Git (and GitHub), so the commit history is preserved. If the consensus is for subversion, I can do that as well. I'll be doing a test conversion of the ODBC repository this weekend. If it is quick to do, I'll also do a test conversion of the docs repository. Mark -- Mark Rotteveel -- 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
Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th
I agree with the git option too. Cheers, Norm. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.-- 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
Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th
On 8-10-2017 21:03, Paul Vinkenoog wrote: To all committers: SourceForge have announced that they plan to terminate CVS read-write support on November 30. The CVS manual module will still be available after that for checkouts and updates, but not for commits. That means that we have around 7 weeks to implement another solution. Options are: - convert the module to SVN on SourceForge; - convert the module to Git on SourceForge; - convert the module to and host it somewhere else. Given the nature, and low traffic, of our module, I'm inclined to go for in-place conversion to SVN. But the other options are also feasible. Any opinions? I think it would be preferable if the documentation project would move to GitHub (https://github.com/FirebirdSQL), where the main project resides. If complexity of git is a problem: GitHub also allows subversion access to a git repository: https://help.github.com/articles/support-for-subversion-clients/ I am willing to spend some time to test and perform the conversion of the manual module to Git (and GitHub), so the commit history is preserved. If the consensus is for subversion, I can do that as well. Just a heads up: This is also being discussed in firebird-admin. Mark -- Mark Rotteveel -- 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
Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th
On 09.10.2017 8:27, Jiří Činčura wrote: Convert to Git and put it under FirebirdSQL organization on GitHub for extra visibility. It might even help with contributions. +1 Regards, Alexey -- 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
Re: [Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th
Convert to Git and put it under FirebirdSQL organization on GitHub for extra visibility. It might even help with contributions. -- Mgr. Jiří Činčura https://www.tabsoverspaces.com/ -- 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
[Firebird-docs] ATTN committers: SourceForge to terminate CVS support on November 30th
To all committers: SourceForge have announced that they plan to terminate CVS read-write support on November 30. The CVS manual module will still be available after that for checkouts and updates, but not for commits. That means that we have around 7 weeks to implement another solution. Options are: - convert the module to SVN on SourceForge; - convert the module to Git on SourceForge; - convert the module to and host it somewhere else. Given the nature, and low traffic, of our module, I'm inclined to go for in-place conversion to SVN. But the other options are also feasible. Any opinions? Cheers, Paul Vinkenoog -- 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
