On Mon, Aug 2, 2021 at 11:34 AM Bartosz Golaszewski <brgl@xxxxxxxx> wrote: > It's actually my fault. Let me explain: the development of the v2 API > for the entire project (C, C++ and Python parts) happens in the > next/libgpiod-2.0 branch of > git://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git I squash the > new changes into the big patch with the plan of resending it for a > final review once we agree on the interface (more or less anyway). > That will allow the repo to remain bisectable. Then we'll be able to > fine-tune different elements. Understood and sensible. Thanks for clarifying. > Maybe you could wait until I post v4? I'm addressing a lot of issues > in this revision. Previous small patches have already been squashed > and they concerned the core C library anyway. Sounds like a plan. I've noticed that, both in the mailing list and your recent commits into next/libgpiod-2.0 (which is why I wondered what the mode of operation is for these changes). Once v4 is out, I will look to review. > There's no target, it'll be ready when it's done. Again, understood and sensible. > PS How did the move go? Very well, thank you. Setup with everything I've brought over to Romania, with a little more to be shipped over very soon. On a somewhat related topic, I'll be reaching out to you directly over the next few days (mainly regarding your relationship / work with BayLibre, if that's okay). Jack