What I would suggest to do is to create a script to forms the merged repository (so we can verify that "git blame" will still work as intended). If there is consensus about doing this generally, we can then debate the structure of the repo and other details. For example, it could be similar to Apache Thrift's repo structure
On Mon, Feb 26, 2018 at 9:32 AM, Deepak Majeti <[email protected]> wrote: > +1. Compatibility benefits will be worthy. > > On Mon, Feb 26, 2018 at 12:48 AM, Nong Li <[email protected]> wrote: > >> I think this is a great idea. Let me know if I can help. >> >> On Sat, Feb 24, 2018 at 4:07 PM, Wes McKinney <[email protected]> wrote: >> >> > hi folks, >> > >> > in a past sync we discussed the prospect of combining all of the >> > Parquet subprojects into a single code repo. Since there are some >> > other programming languages which may join the fold (Rust, C#.NET), it >> > would be beneficial to combine everything into a single repository to >> > assist with integration and compatibility testing. >> > >> > Subprojects (C++, Java, etc.) could still have their own versioned >> > releases. >> > >> > Is this still of interest to the community? I would be willing to >> > assist with this effort. In theory the repo merge could be performed >> > without loss of git history in the respective projects. >> > >> > - Wes >> > >> > > > > -- > regards, > Deepak Majeti
