quilt-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Quilt-dev] address@hidden: quilt: any interest in detecting patch chang


From: Martin Quinson
Subject: [Quilt-dev] address@hidden: quilt: any interest in detecting patch changes while applied?]
Date: Mon, 27 Sep 2004 10:00:32 +0200
User-agent: Mutt/1.5.6+20040722i

This is a case of "please post to the relevant mailing list" ;)

Bye, Mt.

----- Forwarded message from Chris Friesen <address@hidden> -----

Date: Fri, 24 Sep 2004 10:54:44 -0600
From: Chris Friesen <address@hidden>
To: address@hidden, address@hidden,
        Andrew Morton <address@hidden>
Subject: quilt:  any interest in detecting patch changes while applied?

I'm wondering if you would have any interest in detecting patch changes 
while they're applied.

The scenario I have in mind is where I have "patches" symlinked to some 
shared RCS.  I apply some patches.  In the meantime, someone modifies one of 
the patches.  I sync my RCS.  The patches directory is now out of date with 
what is actually applied on my tree, and new patches may not apply even 
though I have all the old patches applied.

What I had in mind was storing the md5 checksum of each patch file as it is 
applied in a .md5 file in the patch directory in .rc.  Whenever I go to 
apply another patch (or maybe to refresh the existing patch), I scan the 
list of applied patches and compare their checksums against the checksums of 
the patch in the patches directory.  If any of them are different, print the 
name of the patch with an error message and suggest that the user pop all 
patches above the earliest changed one and then push them back on.

Would this make sense?  Or is this a case of "don't do that"?

Thanks,

Chris

----- End forwarded message -----

Attachment: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]