Re: [Monotone-devel] Subdirectory support

[Adam Logghe]

Hmmm,

I think thats a good use case... I hope some other folks have some input
 too because as I mentioned before "take my advice, I'm not using it" ;)

I think the answer changes depending on how much you are editing
upstream and importing upstream changes. Trying to track lots of changes
in your dependencies is going to hurt no matter the tool.

I would probably make use of the "cert" function (section 6.5 in the
manual). You can add arbitrary tags to a branch.

You might tag everything with a common version number or perhaps a
pregenerated common datetime (use something sortable without datelibs)
when you have a specific "complete" commit or everytime (something about
this one bugs me..)

You might also tag it with the hash+branch name of the current head of
your main branch. I think I would lean more towards this, and I would
name the tag something very descriptive for clarity.

Adam



Jean Pierre LeJacq wrote:
> On Sun, 23 May 2004, Adam Logghe wrote:
>
>
>>Further- wouldn't your problem be more simply solved by using basic
>>shell scripting? I would think one of the only operations you want to do
>>"all at once" would be something like a checkout. Most other operations
>>would get unmanageable if you were doing them all at once ie merges etc.
>>Commits generally deserve individual comments (and consideration) for
>>another example.
>
>
> I'm not sure I agree.  I running into this issue myself right now
> (essentially trying to replicate CVS's module facility).  I can use
> a script to check out subcomponents that are on individual branches.
> The problem I have now is how to "tag" all branches so as to have a
> true atomic commit.  That would allow me to return to an older
> version of the entire project made up of multiple branches.
>
> Any ideas on the right pattern to use in Monotone?
>