On Aug 26, 2009, at 5:29 PM, Brady Eidson wrote:
On Aug 26, 2009, at 5:26 PM, Mark Rowe wrote:
On 2009-08-26, at 17:19, Brady Eidson wrote:
On Aug 26, 2009, at 4:20 PM, Mark Rowe wrote:
On 2009-08-26, at 15:43, Maciej Stachowiak wrote:
On top of that sometimes the ChangeLog merges cleanly but puts
your entry underneath others, and then you have to open the
file and move your entry back to the top. Sometimes I have not
noticed this and then I land with someone else's commit message.
I just don't get why people are willing to put up with this.
It's really driving me crazy.
One possibility is to have a commit hook that builds the
ChangeLog entry and includes it in the commit atomically - that
way there are no races.
Hooks in Subversion cannot mutate the transaction that is taking
place so I don't think this is an option.
Is there any sort of guarantee that a post commit hook for
revision N will complete before the post commit hook for revision
N + 1 executes?
Couldn't that accomplish this?
Generating two SVN revisions for each change would be awful.
And - I honestly don't know the answer to this - there's actually
*NO* way to alter a previous commit in SVN, even when you have full
access to the server?
Yes, you take down the subversion service, dump the repo to a file,
edit it, then reload. WebKit's repo would take a long time to do this
(hours at least). Then everyone with a working copy would need to
checkout from scratch to get the "new" repo.
You can alter commit messages after the fact quite easily, but not
actual files.
-Bill
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
