On 2019-04-18 15:52, Andreas Krey wrote:
On Wed, 17 Apr 2019 21:29:39 +0000, Johnny Billquist wrote:
...
Uh... If you want to make sure the tree is up to date, you should do a
svn update, not svn commit.
An update doesn't help. It reduces the window in which someone
else could commit a breaking change, but it doesn't close it.
I'd need an atomic commit-when-there-are-no-updates-pending.
Admittedly, this is mostly an academic point, since usually
you don't break other's code this way.
Right, but that is again a different question. If you want the tree to
be up to date, you should do an update, not a commit.
The problem of knowing your tree is up to date when doing a commit is a
different one.
But yes, this is getting rather academic.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: b...@softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
