Zhang, I think the best approach is give us a better explanation about this new feature and how this can help us to archive the desired feature (support multiple languages). Than if the majority agree than I can do the merge, just like I did before, but in another branch.
Let me know if makes sense, ok? Taka Em ter, 16 de out de 2018 às 14:00, Luciano Resende <luckbr1...@gmail.com> escreveu: > So, what is the POC, is it a refactoring of the existing repo? Or is > it a new rewrite of the repo? > > Just asking as it might make sense to make it a branch then actually a > thing in parallel, as this will have an effect for releases, etc. but > you guys know more here than I do. > > Also, it's probably good to have a write up of the main direction of > the design that can help people get familiar with the new approach. > On Tue, Oct 16, 2018 at 11:12 AM Zhang Yifei <yifei.z.l...@gmail.com> > wrote: > > > > Hey guys, > > > > We have reorganized the Poc repo, and want to merge it to our Apache > repo. > > Just making sure here before we do the merge, because im not sure if > doing > > this will perserve the Git commit history. > > What we are planning to do is: > > > > git filter-branch --subdirectory-filter <git origin_repository directory> > > -- --all > > mkdir POCs/ > > git mv * POCs/ > > git commit -m "colleted the data to move" > > > > git clone <git destination_repository_url> cd <git > > destination_repository_directory> git remote add origin_repository_branch > > <git origin_repository directory> git pull origin_repository_branch > master > > --allow-unrelated-histories git remote rm origin_repository_branch > > > > > > Thanks in advance ! > > > > -------------------------------------------------------------- > > Zhang Yifei > > > > -- > Luciano Resende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ >
