On Tue, 2003-10-21 at 16:41, Peter Braam wrote:
No, this is not how we use it. We have patch.diff and a family of
closely related patches (almost identical say) for other kernels.
We modify patch.diff. Now we want to tell someone else what we did to
the tree which contains patch.diff, so that they can easily modify all
the related patches.
So this has nothing to do with forking.
Is this clear?
I think so.
Forking actually is not relevant, anyway. With the snapshot command
(this is what I've called it for now), you would do this:
$ quilt snapshot
# do something (push/pop/modify patches, etc.)
$ quilt diff --snapshot
The result would be a diff between the snapshot and the current state,
no matter how that state looks. Isn't this the functionality you need?
Cheers,