Re: [Firebird-docs] Consider migrating to GitHub?

2016-12-19 Thread marius adrian popa
One argument i can give is that i can edit directly the files on github , so that is a lot faster for small fixes for the doc area On Mon, Dec 19, 2016 at 7:13 PM, Mark Rotteveel wrote: > On 19-12-2016 11:08, Lester Caine wrote: > > On 18/12/16 11:19, Mark Rotteveel wrote:

Re: [Firebird-docs] Consider migrating to GitHub?

2016-12-19 Thread Mark Rotteveel
On 19-12-2016 11:08, Lester Caine wrote: > On 18/12/16 11:19, Mark Rotteveel wrote: >> Git != GitHub. > > But it's the reason most projects use as an excuse to promote git over > other options :( > And it's trying to promote itself as yet another social media site > detracts from the REAL jobs

Re: [Firebird-docs] Consider migrating to GitHub?

2016-12-19 Thread Mark Rotteveel
On 19-12-2016 11:39, Andre van Zuydam wrote: > So bouncing in here on a tangent, I've done this with a couple of > Source forge projects, simply set Source forge to clone the Github > project or visa versa. The only reason I would suggest having things on > Github is for more visibility. Anyway

Re: [Firebird-docs] Clarification for MON$RECORD_STATS

2016-12-19 Thread Köditz , Martin
Ah, makes things clearer. Thank you, Paul. -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot___

Re: [Firebird-docs] Clarification for MON$RECORD_STATS

2016-12-19 Thread Paul Beach
>From Helen's bible... 1. MON$RECORD_BACKOUTS Number of records where a new primary record version is backed out due to a rollback or savepoint undo 2. MON$RECORD_PURGES Number of records where the record version chain is being purged of versions no longer needed by OAT or younger

[Firebird-docs] Clarification for MON$RECORD_STATS

2016-12-19 Thread Köditz , Martin
Hi, currently I translate the chapter about monitoring tables. I'm a bit confused in section MON$RECORD_STATS. Please show the differences of following columns: 1. MON$RECORD_BACKOUTS 2. MON$RECORD_PURGES 3. MON$RECORD_EXPUNGES I need more details here. Especially for

Re: [Firebird-docs] Consider migrating to GitHub?

2016-12-19 Thread Andre van Zuydam
So bouncing in here on a tangent, I've done this with a couple of Source forge projects, simply set Source forge to clone the Github project or visa versa. The only reason I would suggest having things on Github is for more visibility. Anyway my five cents. You can still continue to commit as

Re: [Firebird-docs] Consider migrating to GitHub?

2016-12-19 Thread Lester Caine
On 18/12/16 11:19, Mark Rotteveel wrote: > Git != GitHub. But it's the reason most projects use as an excuse to promote git over other options :( And it's trying to promote itself as yet another social media site detracts from the REAL jobs that many years ago SF did so well but without actually

Re: [Firebird-docs] Consider migrating to GitHub?

2016-12-19 Thread Köditz , Martin
Though I'm a programmer, I find it very hard to use CVS. I had some problems using CVS when Helen committed some changes. I feel more comfortable using git. >> SourceForge itself considers CVS deprecated, and having the repository >> on GitHub might increase visibility and will likely lower the