-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Your question seems to imply that developers are creating branches
> often -- is this because they're creating "task branches" and merging
> back to the trunk frequently? You might find a model where everyone
> checks into the trunk is less overhead.
It's less overhead, but it's also a good way to end up with a broken
trunk.
A better way might be to manage the merges by insisting that merges
back into the trunk contain a suitable log message, which will allow
someone to quickly look through the logs and see how recently each
person has merged back into the trunk. If the log files are properly
structured, you could even write a script to automatically generate a
report (and you can use a pre-commit hook script to ensure that all
logs are properly structured). Really, it shouldn't even be all that
difficult to write a script that would parse through the log files and
compare them with the commit times for modifications to each branch to
prepare a report that would show you which branches had modifications
that weren't committed to the trunk.
- -Bill
>
> Cheers,
> Mike.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFBRbaaSwe0AHUdEwQRAnnPAKDVvWhiRqYXAAFdcpo44wYCRc2zpQCeNI8K
LQ/l/iZgwT6zOu0uv4mOc84=
=Qq/5
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 13 17:03:24 2004