search for: 23bef19412

...uido both use DVCS's and the authoritative upstream is whatever URL the BDFL says it is. Monotonic version numbers are the biggest advantage. It is easy to see that r1234432 contains the bug fix introduced in r1234430. It is very hard to see if version 23bef194ac contains the bug fix added in 23bef19412. This makes interaction with bugzilla and so on much easier. If someone says 'please test r1245145 - should be fixed' you can easily check whether you are running r1245145 or newer. David

...use DVCS's and the authoritative upstream is whatever URL the BDFL says it is. > > Monotonic version numbers are the biggest advantage. It is easy to see that r1234432 contains the bug fix introduced in r1234430. It is very hard to see if version 23bef194ac contains the bug fix added in 23bef19412. This makes interaction with bugzilla and so on much easier. If someone says 'please test r1245145 - should be fixed' you can easily check whether you are running r1245145 or newer. > > David git branch --contains 23bef19412 This will tell you which of your branches have that comm...

...uthoritative upstream is > whatever URL the BDFL says it is. > > > > Monotonic version numbers are the biggest advantage. It is easy to see > that r1234432 contains the bug fix introduced in r1234430. It is very hard > to see if version 23bef194ac contains the bug fix added in 23bef19412. > This makes interaction with bugzilla and so on much easier. If someone > says 'please test r1245145 - should be fixed' you can easily check whether > you are running r1245145 or newer. > > > > David > > git branch --contains 23bef19412 > > This will tel...

...the BDFL says it is. >>> > >>> > Monotonic version numbers are the biggest advantage. It is easy to see >>> > that r1234432 contains the bug fix introduced in r1234430. It is very hard >>> > to see if version 23bef194ac contains the bug fix added in 23bef19412. This >>> > makes interaction with bugzilla and so on much easier. If someone says >>> > 'please test r1245145 - should be fixed' you can easily check whether you >>> > are running r1245145 or newer. >>> > >>> > David >>&gt...

...gt; whatever URL the BDFL says it is. >> > >> > Monotonic version numbers are the biggest advantage. It is easy to see >> > that r1234432 contains the bug fix introduced in r1234430. It is very hard >> > to see if version 23bef194ac contains the bug fix added in 23bef19412. This >> > makes interaction with bugzilla and so on much easier. If someone says >> > 'please test r1245145 - should be fixed' you can easily check whether you >> > are running r1245145 or newer. >> > >> > David >> >> git branch --...

...gt; whatever URL the BDFL says it is. >> > >> > Monotonic version numbers are the biggest advantage. It is easy to see >> > that r1234432 contains the bug fix introduced in r1234430. It is very hard >> > to see if version 23bef194ac contains the bug fix added in 23bef19412. This >> > makes interaction with bugzilla and so on much easier. If someone says >> > 'please test r1245145 - should be fixed' you can easily check whether you >> > are running r1245145 or newer. >> > >> > David >> >> git branch --...

...t;>> > >>>>> > Monotonic version numbers are the biggest advantage. It is easy to see >>>>> > that r1234432 contains the bug fix introduced in r1234430. It is very hard >>>>> > to see if version 23bef194ac contains the bug fix added in 23bef19412. This >>>>> > makes interaction with bugzilla and so on much easier. If someone says >>>>> > 'please test r1245145 - should be fixed' you can easily check whether you >>>>> > are running r1245145 or newer. >>>>> > &gt...

>> clock skew (which is easy to get in a VM) can confuse Ninja in a way >> that doesn't give helpful errors. > >This is a significant issue. I would not want to transition to >cmake+ninja before this is fixed. Do you mean in the same way that clock skew would affect Make? Or just that Ninja doesn't provide that nice "clock skew detected" message that Make

David Chisnall <David.Chisnall at cl.cam.ac.uk> writes: > clock skew (which is easy to get in a VM) can confuse Ninja in a way > that doesn't give helpful errors. This is a significant issue. I would not want to transition to cmake+ninja before this is fixed. -David