Looks good for me. Here is one more suggestion: extract DDEX sources to separate repository, and use FirebirdSql.Data.FirebirdClient rep only for client itself.
On 22 March 2016 at 22:12, Jiří Činčura <j...@cincura.net> wrote: > Hi *, > > I'm contemplating renaming some folders - the two top level folders to > be precise > (https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient/tree/rename). > So the names make a bit more sense as the codebase evolved. Yes? No? > > With the FB 3 protocol work I'm doing right now I'm kind of in a "you > can't make an omelette without breaking eggs" mode. Refactoring all over > the place. :) Like this polishing > https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient/commit/e166e84c2f5409d91b723a5d03930cf2b08a1662. > :) > > -- > Mgr. Jiří Činčura > Independent IT Specialist > > ------------------------------------------------------------------------------ > Transform Data into Opportunity. > Accelerate data analysis in your applications with > Intel Data Analytics Acceleration Library. > Click to learn more. > http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140 > _______________________________________________ > Firebird-net-provider mailing list > Firebird-net-provider@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140 _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
