Re: [Monotone-devel] How to split a project

[Judson Lester]

There's the more immediate case, even, of discovering that part of one project is really a module that should be shareable - you'd like to pull it out into its own branch, delete files on both sides, and then merge_into_dir the module's branch.  Alas, since they share a common parent, this is forbidden.  I have a rough understanding that there's some more-than-trivial complication with making that possible, but I'm not clear on what it is.

Judson

On Mon, Feb 22, 2010 at 6:45 AM, <address@hidden> wrote:

Let's say I have some code checked in along some branch.  Over the year
it has evolved so that it has become two separate programs, that don't
share any code any more, and make sense to develop independently.

Evidently, it makes sense to make two branches, one for each program.
The obvious way is just start new branch(es) and in each branch delete
all the files now belonging to the other.

BUT.  If years down the line, someone wants to include both these
programs into another project, I don't want the merge saying, let's
merge all these changes.  Looky here, all the files of each branch have
been deleted on the other.  There's nothing left!  And that someone
mysteriously end up with no files instaed of all the files.

Is there a better way to split a project?  If not, should there be?

Or,

Am I worrying about nothing?

-- hendrik



_______________________________________________
Monotone-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/monotone-devel