Re: gcc source management requirements

Peter Davis wrote:

>(2f): I'm not quite sure what this is asking, but AFAIK Subversion doesn't
>create "microbranches" to resolve conflicts. Conflicts are resolved in the
>working copy, but remember that copies of all three versions of a merged file
>are available. How would "microbranches" be used and why are they necessary?
>
It's the way a real changeset engine (which Subversion isn't) works.
BitKeeper is an example, Arch probably is, too.

>(5): Automatic ChangeLog updates are in the domain of a new post-commit
>script. Sounds like an interesting idea, but supporting GCC's or any other
>project's specific changelog format -- not to mention enforcing humans to use
>a machine-parseable log message format -- is something that should be handled
>elsewhere.
>

No, "svn log" _is_ an automatic ChangeLog generator, as long as the
commit log format is maintained. There's not only no need to maintain
ChangeLog files in the repository, it's much better _not_ to have them,
as they only complicate merging.

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org