[oe] Request for help on daggy fixes and NCC

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Holger Freyther schreef:

| Sadly this merge triggers another NCC and I think the danger of breaking
| something in manually fixing the NCC is higher than the use of a daggy
fix.
| So what is your opinion on this? Would you do daggy fixes? Would you
avoid
| them? Would you first try and see if the result is mergable?
|
| Thankfully I could use mtn db to kill the daggy fix rev manually and
now need
| to apply the fix on top. And I love the concept of the daggy fix :(

My experience with OE developers is that daggy fixed is such a non-cvs
concept that if one would do a daggy fix, people would start bitching on
IRC about creating multiple heads and a 'bogus' merge for working of an
'old' OE tree.

If only monotone had something like 'hg transplant'....

regards,

Koen

PS: daggy fixes rock!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFH7mqEMkyGM64RGpERAk31AJ9o7mvrhEGSOEebHyAJLE7xR3ldeACeMNGT
+ombgToVwHZ4lo0cV9n3G3g=
=5I31
-----END PGP SIGNATURE-----