From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Request for help on daggy fixes and NCC
Date: Sat, 29 Mar 2008 17:12:52 +0100 [thread overview]
Message-ID: <fslpq4$5dq$1@ger.gmane.org> (raw)
In-Reply-To: <200803291626.09506.zecke@selfish.org>
-----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-----
prev parent reply other threads:[~2008-03-29 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-29 15:26 Request for help on daggy fixes and NCC Holger Freyther
2008-03-29 16:12 ` Koen Kooi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='fslpq4$5dq$1@ger.gmane.org' \
--to=koen@dominion.kabel.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.