-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Daniel Macks wrote:
Patch-tracker #768801.
Comments on either the idea or implementation?
I'm not sure what I think. My problem with it is that it makes one of
the most common development patterns more difficult.
Normally when I'm porting something, I'll put together a basic info
file, go to another window, build it, and wait for it to die. I go in,
make some changes, and generate a patch:
diff -uNr foo-pristine foo > /path/too/foo.patch
Then I build again, and start over. If there's something wrong, I run
the diff again.
If patches are embedded in the info file, every time I want to generate
a patch I need to delete the patch at the end of the info, close the
info file, generate the patch, and then re-edit the info file to make
other changes.
Not only that, but now we're relying on patch not accidentally thinking
anything in the info file is a directive to start a patch (I don't know
if it's been done, but I can imagine bits of diff being part of a
"DescPort" comment or something similar).
- --
Benjamin Reed a.k.a. Ranger Rick -- http://ranger.befunk.com/
<jbeimler> yeah, rpm is for people who can't keep track of hundreds
of scraps of paper
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/DYOaUu+jZtP2Zf4RAhHUAJ9vItsjAb7yNWeLIaNZWbxw4F2HewCgmuA9
6xBHdL2g4Uk8kQSpvypzils=
=xZY0
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
|
