Menu
▾
▴
firebird-docs — chat stuff about documentation
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
(1) |
Mar
|
Apr
(36) |
May
(56) |
Jun
(1) |
Jul
(5) |
Aug
(3) |
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
|
Feb
|
Mar
(15) |
Apr
(5) |
May
(7) |
Jun
(5) |
Jul
(3) |
Aug
(6) |
Sep
(3) |
Oct
(8) |
Nov
(23) |
Dec
(21) |
| 2003 |
Jan
(25) |
Feb
(37) |
Mar
(59) |
Apr
(11) |
May
(8) |
Jun
(24) |
Jul
(18) |
Aug
(29) |
Sep
(30) |
Oct
(11) |
Nov
(20) |
Dec
(5) |
| 2004 |
Jan
(43) |
Feb
(24) |
Mar
(61) |
Apr
(14) |
May
(23) |
Jun
(50) |
Jul
(13) |
Aug
(56) |
Sep
(55) |
Oct
(64) |
Nov
(94) |
Dec
(27) |
| 2005 |
Jan
(40) |
Feb
(10) |
Mar
(55) |
Apr
(20) |
May
(16) |
Jun
(6) |
Jul
(58) |
Aug
(38) |
Sep
(5) |
Oct
(6) |
Nov
(71) |
Dec
(99) |
| 2006 |
Jan
(6) |
Feb
(15) |
Mar
(22) |
Apr
(9) |
May
(31) |
Jun
(35) |
Jul
(47) |
Aug
(18) |
Sep
(21) |
Oct
(24) |
Nov
(63) |
Dec
(79) |
| 2007 |
Jan
(22) |
Feb
(40) |
Mar
(47) |
Apr
(69) |
May
(22) |
Jun
(20) |
Jul
(25) |
Aug
(13) |
Sep
(7) |
Oct
(44) |
Nov
(76) |
Dec
(1) |
| 2008 |
Jan
(26) |
Feb
(30) |
Mar
(120) |
Apr
(14) |
May
(22) |
Jun
(40) |
Jul
(48) |
Aug
(7) |
Sep
(34) |
Oct
(31) |
Nov
|
Dec
(30) |
| 2009 |
Jan
(9) |
Feb
(6) |
Mar
(9) |
Apr
(2) |
May
(9) |
Jun
|
Jul
(31) |
Aug
(32) |
Sep
(15) |
Oct
(23) |
Nov
|
Dec
(9) |
| 2010 |
Jan
(19) |
Feb
(9) |
Mar
|
Apr
|
May
(9) |
Jun
(6) |
Jul
(8) |
Aug
(21) |
Sep
(10) |
Oct
(1) |
Nov
(3) |
Dec
(33) |
| 2011 |
Jan
|
Feb
(1) |
Mar
(4) |
Apr
(10) |
May
|
Jun
(9) |
Jul
(23) |
Aug
(2) |
Sep
(35) |
Oct
(36) |
Nov
|
Dec
(4) |
| 2012 |
Jan
(3) |
Feb
(8) |
Mar
(3) |
Apr
|
May
|
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
(12) |
Nov
(12) |
Dec
|
| 2013 |
Jan
(18) |
Feb
(5) |
Mar
(1) |
Apr
|
May
|
Jun
(5) |
Jul
|
Aug
(21) |
Sep
|
Oct
(5) |
Nov
(1) |
Dec
(11) |
| 2014 |
Jan
|
Feb
|
Mar
(4) |
Apr
(2) |
May
|
Jun
|
Jul
(2) |
Aug
(5) |
Sep
(6) |
Oct
|
Nov
(29) |
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
(14) |
Apr
|
May
|
Jun
|
Jul
(7) |
Aug
(7) |
Sep
(5) |
Oct
|
Nov
(6) |
Dec
(3) |
| 2016 |
Jan
(14) |
Feb
(9) |
Mar
(33) |
Apr
(12) |
May
(18) |
Jun
(3) |
Jul
|
Aug
(15) |
Sep
|
Oct
|
Nov
|
Dec
(22) |
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(10) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(44) |
Nov
(32) |
Dec
(8) |
| 2018 |
Jan
(2) |
Feb
(25) |
Mar
(16) |
Apr
(11) |
May
(1) |
Jun
(19) |
Jul
(3) |
Aug
|
Sep
|
Oct
(25) |
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
(2) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(3) |
| 2020 |
Jan
(29) |
Feb
(28) |
Mar
(13) |
Apr
(13) |
May
(107) |
Jun
(75) |
Jul
(57) |
Aug
(36) |
Sep
(3) |
Oct
(4) |
Nov
(4) |
Dec
(1) |
| 2021 |
Jan
(2) |
Feb
(13) |
Mar
(5) |
Apr
(6) |
May
(44) |
Jun
(9) |
Jul
(9) |
Aug
(3) |
Sep
(11) |
Oct
(5) |
Nov
(14) |
Dec
(19) |
| 2022 |
Jan
(1) |
Feb
|
Mar
|
Apr
(4) |
May
(1) |
Jun
(1) |
Jul
(13) |
Aug
(6) |
Sep
(2) |
Oct
(7) |
Nov
(2) |
Dec
|
| 2023 |
Jan
(2) |
Feb
|
Mar
(13) |
Apr
(2) |
May
(31) |
Jun
(12) |
Jul
(5) |
Aug
(5) |
Sep
(27) |
Oct
(7) |
Nov
(25) |
Dec
(7) |
| 2024 |
Jan
(11) |
Feb
(27) |
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: marius a. p. <ma...@gm...> - 2017-11-15 10:10:59
|
I have added a pull request https://github.com/FirebirdSQL/firebird-documentation/pull/1 On Wed, Nov 15, 2017 at 12:02 PM, marius adrian popa <ma...@gm...> wrote: > The Old ChangeLog i guess can be removed from git > > https://github.com/FirebirdSQL/firebird-documentation/blob/master/ > ChangeLog > |
|
From: marius a. p. <ma...@gm...> - 2017-11-15 10:02:31
|
The Old ChangeLog i guess can be removed from git https://github.com/FirebirdSQL/firebird-documentation/blob/master/ChangeLog |
|
From: marius a. p. <ma...@gm...> - 2017-11-13 14:14:38
|
mariuz On Mon, Nov 13, 2017 at 4:08 PM, Mark Rotteveel <ma...@la...> wrote: > On 13-11-2017 14:54, marius adrian popa wrote: > >> Could you add me with write access , i wish to contribute to the docs : >> Ubuntu and other areas ... >> > > What is your GitHub username? > > > -- > 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 > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-docs > |
|
From: Mark R. <ma...@la...> - 2017-11-13 14:08:47
|
On 13-11-2017 14:54, marius adrian popa wrote: > Could you add me with write access , i wish to contribute to the docs : > Ubuntu and other areas ... What is your GitHub username? -- Mark Rotteveel |
|
From: marius a. p. <ma...@gm...> - 2017-11-13 13:54:13
|
Could you add me with write access , i wish to contribute to the docs : Ubuntu and other areas ... On Sun, Nov 12, 2017 at 1:03 PM, Mark Rotteveel <ma...@la...> wrote: > The migration from SourceForge CVS to GitHub has been completed. The > repository is at https://github.com/FirebirdSQL/firebird-documentation > (with clone URL gi...@gi...:FirebirdSQL/firebird-documentation.git or > https://github.com/FirebirdSQL/firebird-documentation.git ) > > Members of the firebird-documentation team have write access to the > repository, and in addition to me and Helen, I have given Paul rights to > add (or remove) members from this team. > > Be aware that FirebirdSQL organization members that are marked as 'owner' > also have write access and can manage the team. > > I have disabled the issues and projects features, but left the Wiki > enabled. > > If there are any problems or questions, let me know. > > 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 > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-docs > |
|
From: Köditz, M. <Mar...@it...> - 2017-11-13 12:46:47
|
OK. So I will work on master branch and push my commits directly. Regards, Martin |
|
From: Paul V. <pa...@vi...> - 2017-11-13 12:20:54
|
Mark Rotteveel wrote: > The B_Release branch seems to contain cherry-picked changes from master, > but in general it is outdated compared to master. For example the > Firebird 3 release notes are entirely absent from B_Release (as is your > translation of the langref), and the 2.5 release notes are only up to > 2.5.0. Maybe Paul knows the purpose of this branch. It was created years ago by Dmitri Yemanow. Its purpose is to always have the most recent buildable and publishable version of each document available. So every time you commit something to master and it's publishable, you should also commit it to B_Release. But most committers seem to have forgotten about that (including myself, sometimes). Cheers, Paul Vinkenoog |
|
From: Mark R. <ma...@la...> - 2017-11-13 11:57:42
|
On 13-11-2017 12:01, Köditz, Martin wrote: > Hi Mark, > > I have completed the German translation of chapter DDL. Should I push it > directly? What is the correct branch? I have seen you created a branch > B_Release. Or should I create a merge request? The B_Release branch was migrated from CVS (I didn't create it). The master branch is what is called the HEAD branch in CVS. And the master branch is what you should target for your changes. The B_Release branch seems to contain cherry-picked changes from master, but in general it is outdated compared to master. For example the Firebird 3 release notes are entirely absent from B_Release (as is your translation of the langref), and the 2.5 release notes are only up to 2.5.0. Maybe Paul knows the purpose of this branch. If you want to use pull requests, that means someone has to review and approve it. And given the nature of translations, that would mean you need someone fluent in the language, or you only get a 'mechanical' review. If you used to commit directly to CVS in the past, I don't see why you should change that now. Mark -- Mark Rotteveel |
|
From: Paul V. <pa...@vi...> - 2017-11-13 11:46:47
|
Hi Martin, > Hi Mark, > > I have completed the German translation of chapter DDL. Should I push it directly? What is the correct branch? I have seen you created a branch B_Release. Or should I create a merge request? As for question 2: Everything goes into the trunk, or whatever it's called in Git. Publishable documents go into B_Release as well. This branch was already present in CVS. Your first and last questions should be answered by Mark. Or I could give it a shot and then if you do the exact opposite of what I tell you, it might just be right ;-) Cheers, Paul |
|
From: Köditz, M. <Mar...@it...> - 2017-11-13 11:00:45
|
Hi Mark, I have completed the German translation of chapter DDL. Should I push it directly? What is the correct branch? I have seen you created a branch B_Release. Or should I create a merge request? Regards, Martin |
|
From: Mark R. <ma...@la...> - 2017-11-12 18:20:40
|
On 2017-11-12 17:41, Norman Dunbar wrote: > Thanks for all the hard work on the migration Mark - it is > appreciated. > > Would having issues enabled be better for people to log bugs in the > docs perhaps? As there also is http://tracker.firebirdsql.org/browse/DOC, I thought it would be better to initially disable it. If there is a consensus that enabling issues alongside the tracker is a good idea (or retiring the DOC project in the tracker), then it can always be enabled. Mark |
|
From: Paul V. <pa...@vi...> - 2017-11-12 17:02:54
|
Mark Rotteveel wrote: > The migration from SourceForge CVS to GitHub has been completed. > (...) Thanks for all the work you've done, Mark! I'll have a look at it later tonight. Chers, Paul |
|
From: Norman D. <No...@du...> - 2017-11-12 16:41:49
|
Thanks for all the hard work on the migration Mark - it is appreciated. Would having issues enabled be better for people to log bugs in the docs perhaps? Cheers, Norm. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. |
|
From: Mark R. <ma...@la...> - 2017-11-12 11:03:37
|
The migration from SourceForge CVS to GitHub has been completed. The repository is at https://github.com/FirebirdSQL/firebird-documentation (with clone URL gi...@gi...:FirebirdSQL/firebird-documentation.git or https://github.com/FirebirdSQL/firebird-documentation.git ) Members of the firebird-documentation team have write access to the repository, and in addition to me and Helen, I have given Paul rights to add (or remove) members from this team. Be aware that FirebirdSQL organization members that are marked as 'owner' also have write access and can manage the team. I have disabled the issues and projects features, but left the Wiki enabled. If there are any problems or questions, let me know. Mark -- Mark Rotteveel |
|
From: Mark R. <ma...@la...> - 2017-11-12 10:19:45
|
On 12-11-2017 11:14, Mark Rotteveel wrote: > On 11-11-2017 11:31, Mark Rotteveel wrote: >> I will migrate the CVS manual module to GitHub tomorrow, Sunday 12 >> November, starting at 11:00 CET (10:00 GMT). > > The migration is delayed to later today, I accidentally deleted the > options file with the configuration for the repository migration, so now > I need to reconstruct it and perform some additional verification. False alarm, I had a backup copy in a different location. Mark -- Mark Rotteveel |
|
From: Mark R. <ma...@la...> - 2017-11-12 10:14:38
|
On 11-11-2017 11:31, Mark Rotteveel wrote: > I will migrate the CVS manual module to GitHub tomorrow, Sunday 12 > November, starting at 11:00 CET (10:00 GMT). The migration is delayed to later today, I accidentally deleted the options file with the configuration for the repository migration, so now I need to reconstruct it and perform some additional verification. Mark -- Mark Rotteveel |
|
From: Mark R. <ma...@la...> - 2017-11-11 10:31:09
|
I will migrate the CVS manual module to GitHub tomorrow, Sunday 12 November, starting at 11:00 CET (10:00 GMT). After the migration has begun, commits to CVS for the manual module will be 'lost': they will still be in CVS, but they will not be part of the new repository on GitHub. If this happens, you will need to copy those changes over to the git repository and commit/push them manually. This afternoon I'll be adding the GitHub accounts that I know of to a group. This group will be used for access to the firebird-documentation repository. You'll receive an invite for that. I will send another mail when the migration has been done. PS If you want your old commits to be associated with your GitHub account, then make sure to add your <sourceforgeusername>@users.sourceforge.net email address to your GitHub account. This is entirely optional, but it allows you to view some statistics and history in your profile. -- Mark Rotteveel |
|
From: Köditz, M. <Mar...@it...> - 2017-11-06 14:10:45
|
Hi Mark, my Github username is MartinKoeditz. Regards, Martin -----Ursprüngliche Nachricht----- Von: Paul Vinkenoog [mailto:pa...@vi...] Gesendet: Montag, 6. November 2017 03:28 An: Chatter regarding Firebird documentation <fir...@li...> Betreff: Re: [Firebird-docs] Test repository CVS to git migration 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 and all others are in favour, let's do it! > Hats off to you for your efforts with this and the other CVS repo's, > Mark! Hear, hear! Mark, my Github username is paulvink. Cheers, Paul ------------------------------------------------------------------------------ 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 Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-docs |
|
From: Mark R. <ma...@la...> - 2017-11-06 09:03:05
|
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 weekend (probably Saturday, maybe Sunday) > I still seem to have one or two novice issues on this side but they > are not showstoppers. Over the weekend I cloned the #4 test and used > it to create a private local/remote repository for the Developer's > Guide stuff, as I am using a couple of experimental changes to the build > ingredients. Be aware that you will need to make a fresh clone of the final repository once I've done the 'real' migration. Or at least, otherwise you'll need to do some complex steps to reconcile / merge them. Mark -- Mark Rotteveel |
|
From: Paul V. <pa...@vi...> - 2017-11-06 02:28:04
|
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 and all others are in favour, let's do it! > Hats off to you for your efforts with this and the other CVS repo's, > Mark! Hear, hear! Mark, my Github username is paulvink. Cheers, Paul |
|
From: Helen B. <he...@ii...> - 2017-11-05 18:28:14
|
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 cloned the #4 test and used it to create a private local/remote repository for the Developer's Guide stuff, as I am using a couple of experimental changes to the build ingredients. All is well, so far, I think. It will be a while before I need to push anything to the main repo. I don't think it will be too much of a problem to do that "with rule-book in hand" and Google alongside. Hats off to you for your efforts with this and the other CVS repo's, Mark! Cheers, Helen |
|
From: Norman D. <No...@du...> - 2017-11-04 15:01:04
|
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! > Alternatively, contributors could use forks and use pull requests for > their contributions. I think that this might be the better idea, but it will mean that a "benevolent dictator" (or similar) would be required to actually check and merge the pull requests. It's reasonably simple to have a fork and keep it up to date with a remote pointing at the original repository, and a "git pull" from that remote. Cheers, Norm. -- Norman Dunbar Dunbar IT Consultants Ltd Registered address: 27a Lidget Hill Pudsey West Yorkshire United Kingdom LS28 7LG Company Number: 05132767 |
|
From: Mark R. <ma...@la...> - 2017-11-04 12:42:34
|
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, I had to put these > off. It would be nice to get these people on board. > > So what are the next steps? I'm waiting on Helen to give the final go. I have found one minor issue with .sh files not being marked executable (relevant on Linux), but I have a fix for that. 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. Alternatively, contributors could use forks and use pull requests for their contributions. Mark -- Mark Rotteveel |
|
From: Köditz, M. <Mar...@it...> - 2017-11-02 09:27:22
|
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 get these people on board. So what are the next steps? Regards, Martin |
|
From: Kjell R. <kje...@ma...> - 2017-10-20 08:47:51
|
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 > the bits I need to grokk. > > If I survive that, I might even have a go at cloning the doc branch of > the main repository. As a person who also switched from SVN (not CVS) to Git, I'd recommend the official tutorial: https://git-scm.com/docs/gittutorial I think that was the one I found most instructive. Also, maybe, this one: https://www.tutorialspoint.com/git/index.htm It's funny that when Linus Torvalds started out with Git, his explicit goal was to avoid doing ANYTHING the way SVN does. :-) I don't know how you will handle tags in the docs project, but one thing I find is easy to miss in TortoiseGit is that when you push your local repo to origin, you always need to check the checkbox to include tags. That is, if your local tags are really supposed to be migrated to origin. The checkbox can't be defaulted to checked state. Regards, Kjell |
58 messages has been excluded from this view by a project administrator.
