Re: ANNOUNCE: Debian build scripts on a public Monotone server

Ludovic Brenta schrieb:

I find it interesting in Monotone you can commit changes even if your
tree is not up-to-date, so you only commit your changes first go, and
then you do the merge. As opposed to being forced to do both in the
one commit (I never liked this model).

That's funny because it took me a little while to get used to the
"commit first, merge then" model. I wasn't used to it. Now I like it
quite a lot.

That's exactly was I was always looking for. I just hate how most vcs force me to mess up my perfectly good code by forcing me to merge when I am not yet ready for merge. Worse: I won't have a backup copy of the pre-merge code.

Yes, those vcs will mess up my working copy with ".#" files - but that is not the same as having a backup inside the repository.

The other option I am often missing is a "golden code" option. What I have prepared inside the working copy is right and propper - no merge needed - thank you very much.

Martin
.

Relevant Pages

  • Re: Backups and Transaction Log file size
    ... It sounds like a classic case of a long running open transaction. ... Find the client and either commit or roll it back. ... If you know it is a garbage connection you can kill the SPID and it will roll back any changes that the SPID may have open and allow you to backup and truncate properly. ... Once the committed trans have been ...
    (microsoft.public.sqlserver.setup)
  • Re: Backups and Transaction Log file size
    ... Find the client and either commit or roll it back. ... that a FULL Backup didn't do the Log file, ... Even after I added Transaction Log backups, ... Once the committed trans have ...
    (microsoft.public.sqlserver.setup)
  • Re: Backups and Transaction Log file size
    ... You can try stopping and restarting SQL Server as that will roll back any open trans when it restarts. ... Find the client and either commit or roll it back. ... > that a FULL Backup didn't do the Log file, ... > Even after I added Transaction Log backups, ...
    (microsoft.public.sqlserver.setup)
  • Re: does this backup sequence commit all data to the database
    ... the data was committed when the application transactions were ...  That could be an explicit COMMIT when an explicit BEGIN ... recovery mode there is no reason to backup the log. ... I understand that "backup log testdb to disk = '...'" will backup the ...
    (comp.databases.ms-sqlserver)
  • Re: Exchange Logs not being committed to database
    ... The logs are not flushed until a full ... backup backup ... this prevent the Exchange transaction logs from being committed? ... Could this take days to commit all these files? ...
    (microsoft.public.exchange.admin)