Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Do you really need to check out <strong>ANY</strong> old revision and expect it to build?</p> <p>I agree with you that you should be able to expect that the tip will always build.<br> This can be easily achieved, <a href="https://stackoverflow.com/questions/7518723/how-do-we-manage-granular-changesets-in-the-central-shared-repository/7545143#7545143">like Lazy Badger already said</a>, by some kind of "don't push unfinished work to the main repo" policy / mutual agreement.</p> <p>Concerning older revisions: </p> <ul> <li>if you want to build older official releases of your software again (like, you're at version 1.6 now and want to make an v1.2 executable), you can expect the <code>1.2</code> tag to build as well if everybody always sticked to the "don't push unfinished work" policy.</li> <li>if you want to take <strong>ANY</strong> revision and build it...well, do you really need this? Any bugs in previous versions will probably refer to official releases (see the "<code>1.2</code> tag" stuff above), and not to something in between.</li> <li>if you <strong>really</strong> need a buildable version from in between the official releases (for whatever reason), you'll have to look at the commit messages and find the commit that says <code>feature 'foo' finished</code> (and not the one that says <code>started implementation of feature 'foo'</code>).<br> Yes, this requires a bit of thinking / common sense, but I can't imagine that you will need this really often.</li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload