Hi,

I began a project about six months ago as a single repository. I've
now reached the point where I'd like to split out several files into a
separate library, for use across multiple projects. Of course, I also
want to preserve the history of these files in the new library
repository. However, several of these patches include changes to other
files (eg, in response to changes in module interfaces) and in order
to pull all of the library-specific patches, I end up having to pull
in a large number of additional patches. What I'd like to do is
identify the relevant patches ("darcs changes file1 ... fileN") and
pull modified versions of these patches that do not include any hunks
that modify other files in the repository.

I can't see a more efficient way of doing this than manually applying
and recording individual hunks (using "darcs changes -v file1 ...
fileN", or "darcs annotate --match XXX" and "darcs unrecord --last 1
--matches XXX"). It sounds as though the "amend-record on steroids"
feature would be useful here. Is there another way to achieve (with
darcs 2.8.1) what I'm trying to accomplish?

Thanks for any advice,
Rob
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users

Reply via email to