Re: [Codestriker-user] multiple modules

[Bryce S. <bry...@dy...>]

We have exactly the same use case. We have a few source code trees for
completely different architectures, languages, and processors, and a build
tools tree that all get tagged together for our builds. In our case, though,
I think we can just use the tags on the parent module and get only the
relevant sub-trees, because when we do our tagging we build a piece-meal
sandbox of only the sub-modules that we care about, and do the tag on
those.

On 7/31/07, Mark Keisler <mar...@mo...> wrote:
>
> Has anyone ever requested being able to specify multiple modules for an
> SVN repository (or others)?  I have  a 'customer' who asked about this,
> but it seems more a case of proper SCM technique to me. His request:
> " Creating a new topic that only has one module is inflexible. Suppose a
> developer wants to create a
> topic with two modules M1 and M2 across a huge span of revision numbers.
> Rather than use the
> closest ancestor module A of both modules (and thus include potentially
> a bunch of irrelevant crap
> [subdirs of A]), the developer simply supplys M1 and M2 when s/he
> creates the topic."
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Codestriker-user mailing list
> Cod...@li...
> https://lists.sourceforge.net/lists/listinfo/codestriker-user
>



-- 
Bryce Schober