On Wed, Apr 22, 2015 at 11:03:08AM -0400, Mark H Weaver wrote: > Well, fair enough :) However, since I reverted the libidn-1.30 update > and cancelled all the associated jobs on Hydra, the argument actually > does apply, although that was not clear from this message alone.
Definitely, these two needed to go together. > There's an easy solution for this: click on the little "Compare to..." > button near the top right corner of the evaluation page, and select > "Jobset gnu:master". More generally, visit: > http://hydra.gnu.org/eval/<XXXXXX>?compare=<YYYYYY> > where <XXXXXX> and <YYYYYY> are evaluation IDs. Nifty trick, thanks for sharing! > Does this make sense? It does. Now, I would still like some guidelines for what to commit to master and what to core-updates, that we could possibly write down in HACKING (and update when the hydra situation changes). Does something like "If you modify PACKAGE from base.scm, or 'guix refresh -l PACKAGE' shows that >= N packages are affected, then commit to core-updates" make sense? If yes, what should be the value of N? If not, what would be a better idea? Andreas