What's needed to complete that (if only for fauxton)? Is it just a case of importing code to the new repo and changing origins, or is there more (e.g. Build scripts)?
On Wednesday, 29 January 2014 at 10:03, Benoit Chesneau wrote: > On Wed, Jan 29, 2014 at 11:00 AM, Alexander Shorin <kxe...@gmail.com> wrote: > > > While we're going to multirepos does this really need? > > I think it's good reminder to migrate project structure ASAP to reduce > > overall annoying level (; > > > > > agree, but until we go to that ... > > - benoit > > > -- > > ,,,^..^,,, > > > > > > On Wed, Jan 29, 2014 at 1:55 PM, Benoit Chesneau <bchesn...@gmail.com> > > wrote: > > > There are a lot of fauxton commits landing in master. Which is fine I > > > > guess > > > but that makes it hard to check other commits. Can you eventually tag > > > > them > > > with "fauxton:" or whatever saying fauxton. It will be a lot easier to > > > filter when looking for other patches. > > > > > > Thanks! > > > > > > - benoit
