Emails about IMP build failures now go to the IMP-build mailing list,
rather than IMP-dev. This makes the IMP-dev mailing list archives a
little tidier (no longer cluttered with those emails).
If you were subscribed to IMP-dev, you are also subscribed to IMP-build.
IMP-build contains topic filters, which you can see if go to the
IMP-build info page (https://salilab.org/mailman/listinfo/imp-build) and
click on 'Unsubscribe or edit options', then log in and scroll down the
page. You can …
[View More]use these to choose to get only a subset of build failure
messages. For example, if you only work on SAXS, you can select the saxs
and saxs_merge filters and then only get an email if the IMP.saxs module
or the saxs_merge application fails. (If you select no filters, you get
any email if any part of IMP fails, same as before.)
If you want to discuss IMP development but don't actually work on any
IMP code, you can unsubscribe from IMP-build if you so choose. The build
system results page (http://salilab.org/imp/nightly/tests.html) is still
public, of course.
Ben
--
ben(a)salilab.org http://salilab.org/~ben/
"It is a capital mistake to theorize before one has data."
- Sir Arthur Conan Doyle
[View Less]
I added a little script to IMP tools called show-changes that shows
changes in IMP (as announced in the history file) that have occurred
since you last updated. The idea is to help people get an idea if
there are any changes that would require updating their code before
doing svn update so you don't have to spend time updating your code
when you are in the middle of something else. And I hope to encourage
people to read the change log so they have a sense of what is
happening in IMP.
Do ./…
[View More]tools/show-changes from you svn checkout to see what it says. Let
me know if there are any problems.
[View Less]
I added emacs config code to a new emacs page in the wiki that:
- turns characters beyond the 80 character limit red
- removes blank spaces and the ends of lines when you save.