I've wondered a few times if there's any way to do a special sort of
'darcs get' to get a new repo with only certain files in it?  For
instance, suppose I have repo A with files a, b, c, and d.  And I want
to end up with a repo B with just files a and b?  (in particular, A
might be a private repo and I just want to make a subset of it public
- maybe c and d contain personal information in them...  or maybe it's
just a really big repo and I want to reduce the overhead from files
that aren't relevant)

So what I want is something to go through all the patches (in reverse
order, presumably, to track renames, etc) and only cherry-pick the
changes that pertain to the files I want, and then pull these
cherry-picked changes into a new repository.  Thus, the history is
maintained on the files I wanted to get, while everything else is left
behind.

Is this at all possible at the moment (short of writing a rather
frightening perl script to pull patches one at a time, deleting
extraneous files, and then amend-recording... on second thought this
doesn't work anyway)?

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

Reply via email to