-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: |> Nice work, I am just a bit worried that some of these files like ts.h |> and irqs.h are really not "controlled" by us but by upstream, won't we |> see conflicting or at least duplicated moves coming in from upstream soon? | | Upstream has already moved everything to the new location; a vanilla | kernel does not have the include/asm-arm/arch-s3c2410 directory | anymore. Everything that's lagging is Moko stuff. Anyway, git is | pretty smart about these things. Even if somebody else were to do the | same move, the changes would match and git-rebase would just discard | the patch. What we get from this is a chance to see when changes that | clash with Moko work are landing upstream... with the two separate | directories we were missing this.
Yes I didn't see it made trouble and put them on stable-tracking last night, but now I'm worrying that we have "moko stuff" calling itself something like mach/pwm.h... I guess the sooner we have those conflicts and resolve them the better. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkj3A8UACgkQOjLpvpq7dMpPsACfXsKrhTiQKol3jclyGpYE+utp seMAnR14GYTDeqYSgcvQEkpZqvARJk/v =dTyJ -----END PGP SIGNATURE-----
