Re: Re: Idea: embed patch in .info

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

Max Horn wrote:

> Point taken, you are right of course!
> Still I'd be interested to know if somebody has already had any real 
> experiences with this (independent of the subject of the thread, 
> actually). E.g. I converted a few of my packages to the new scheme, but 
> did not yet update any of them again. I wonder if people maybe already 
> have had a chance to make use of the "see the history more easily" feature.

I've used it extensively in my exp tree to tell what I changed in KDE 
packages and stuff.  I use that pattern of behavior (things like 'cvs 
log <foo>' and then doing a diff against certain milestone revisions) 
all of the time in other projects too.

It's also a good way to see what's changed since a given time, eg, you 
can do "cvs diff -D <date>" on an info file to see what's been modified.

I can tell you now that even if no one else gets any use out of it, I 
will be using it constantly.  :)

- -- 
Benjamin Reed a.k.a. Ranger Rick -- http://ranger.befunk.com/
Standards are the industry's way of codifying obsolescence.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/DyMmUu+jZtP2Zf4RAjxDAKCL/bakYyTTycBxu29EF8+BU0UYPgCgnNdV
Z9RMNfTtgz1EoKCTLzTQkyw=
=VjV9
-----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/bulletproofapps1