Suppose you're opening an issue and there's a lot noisey logs that may be useful.
Rather than wrecking readability, wrap it in a <details>
tag!
<details>
Summary Goes Here
Ok, I geeked out, and this is probably more information than you need. But it completely answers the question. Sorry. ☺
Locally, I'm at this commit:
$ git show
commit d6cd1e2bd19e03a81132a23b2025920577f84e37
Author: jnthn <jnthn@jnthn.net>
Date: Sun Apr 15 16:35:03 2012 +0200
When I added FIRST/NEXT/LAST, it was idiomatic but not quite so fast. This makes it faster. Another little bit of masak++'s program.
This configuration will manipulate the PATH variable, so that tools that
python
will use python 2. Since we embedd the metdata setting in the job script we set use_metadata_binary
and
Dear training enthusiast,
We have started to work on an unification of the Galaxy training material as discussed during the GCC 2016. As a first example we have chosen our Exome-Seq tutorial and have ported it over to give a real world example of how we imagine the next generation of Galaxy training looks like. Look by yourself: https://github.com/bgruening/training-material/tree/master/Exome-Seq