Clark Rawlins <firstname.lastname@example.org> writes:
> If I understand correctly, subversion commits all of the changes you commit
> at a single time as a single transaction, either they all succeed or fail
> As a cvs user I have created scripts to build changelog information and
> associate the change information with individual files so the changes can be
> committed as comments/logs for each file in the commit process. Are there
> any plans to provide file by file change information and how would that work
> when all of the changes have to be committed at once to be part of the same
The current plan is that log entries are a property of the version ---
a transaction becomes a version when it is successfully committed.
Each transaction you commit should reflect a logically independent,
coherent change. If you do this, then the version created by that
commit acts as a patch number --- others can easily refer to the
change in mail messages, extract it via `svn diff', move it to other
branches, and so on. Each logically coherent change needs a
corresponding log message that explains the whole change. So log
messages are associated with transactions.
This ability doesn't actually restrict you at all:
- If your files each contain independent changes, you should commit
each of them as a separate transaction, with its own log message.
- If you have changes to several files that constitute a single,
coherent change, you should commit them all as a single transaction,
with its own log message.
The `svn log' command will take file/directory names as arguments, and
print the log messages for only those versions in which those files /
directories changed. So you can still access log messages as if they
were attached to changed files.
Received on Sat Oct 21 14:36:13 2006