[darcs-users] Moving changes between different (but similar) projects?

[Nimrod A. Abing]

On 7/29/05, Ketil Malde <ketil.malde at bccs.uib.no> wrote:
> Colin Fleming <colin.mailinglist at gmail.com> writes:
> 
> > I want to create an application skeleton that I and others can use to
> > base new projects on.
>   [...]
> > One problem I can forsee is that if I push changes from one of the
> > applications to the skeleton,  darcs will see a lot of patches for
> > files that don't exist in the skeleton, and will presumably ask me if
> > I want to push them there. Any suggestions for how to handle this?
> 
> Have a separate "skeleton project" which only contains desired
> modifications to the root project, and have other projects pull from
> there?

I find myself in the same predicament as Colin. This is exactly what I
do over here. However as the number of projects forked off from the
root project grows, it becomes a pain to manage the patches being
pushed to or pulled from the root project. See my earlier posting
regarding making "unexportable" patches.
-- 
_nimrod_a_abing_

v1sw5CPJYUhw5ln3pr8OUSck6ma8u7LBw3DWNTm5g/l7DaIs7Rr4e6t5Xb4Op1en3g5RZAHC