Sat, 03 Jan 2009 17:15:21 +0100 mq: lowercase output
Martin Geisler <mg@daimi.au.dk> [Sat, 03 Jan 2009 17:15:21 +0100] rev 7627
mq: lowercase output This extension produces quite a lot of informational messages during its normal operation and it is hard to say which strings can be changed and which cannot.
Sat, 03 Jan 2009 17:15:21 +0100 churn: lowercase output
Martin Geisler <mg@daimi.au.dk> [Sat, 03 Jan 2009 17:15:21 +0100] rev 7626
churn: lowercase output This changes the continuously updated progress bar -- not something a script would rely on.
Mon, 12 Jan 2009 17:51:57 +0100 bdiff: add comment about normalization
Benoit Boissinot <benoit.boissinot@ens-lyon.org> [Mon, 12 Jan 2009 17:51:57 +0100] rev 7625
bdiff: add comment about normalization
Mon, 12 Jan 2009 13:20:09 +0100 Improved hgweb test.
Stefan Ring <stefan@complang.tuwien.ac.at> [Mon, 12 Jan 2009 13:20:09 +0100] rev 7624
Improved hgweb test. The hgweb fix in 069b29656401 aimed at restoring the "back" link in hgweb's filelog that has been lost in 62e0bb41e682. However, the previous version of this test ran the filelog command on a file with only a single filelog entry. In this case, the previous hgweb version did not exhibit the bug. The error condition is now correctly tested with a filelog of 2 entries.
Mon, 12 Jan 2009 09:57:52 +0100 tests: use killdaemons.py in test-highlight
Dirkjan Ochtman <dirkjan@ochtman.nl> [Mon, 12 Jan 2009 09:57:52 +0100] rev 7623
tests: use killdaemons.py in test-highlight
Mon, 12 Jan 2009 09:16:03 +0100 use dict.iteritems() rather than dict.items()
Dirkjan Ochtman <dirkjan@ochtman.nl> [Mon, 12 Jan 2009 09:16:03 +0100] rev 7622
use dict.iteritems() rather than dict.items() This should be faster and more future-proof. Calls where the result is to be sorted using util.sort() have been left unchanged. Calls to .items() on configparser objects have been left as-is, too.
Mon, 12 Jan 2009 09:07:02 +0100 mq: allow qpop if popped revisions are not working dir parents
Dirkjan Ochtman <dirkjan@ochtman.nl> [Mon, 12 Jan 2009 09:07:02 +0100] rev 7621
mq: allow qpop if popped revisions are not working dir parents
Mon, 12 Jan 2009 09:53:55 +0100 mq: refactor the pop code to be more readable and allow more changes
Dirkjan Ochtman <dirkjan@ochtman.nl> [Mon, 12 Jan 2009 09:53:55 +0100] rev 7620
mq: refactor the pop code to be more readable and allow more changes
Mon, 12 Jan 2009 09:13:45 +0100 merge with crew-stable
Dirkjan Ochtman <dirkjan@ochtman.nl> [Mon, 12 Jan 2009 09:13:45 +0100] rev 7619
merge with crew-stable
Fri, 09 Jan 2009 22:15:08 +0000 Bugzilla 2.18 and on use contrib/sendbugmail.pl, not processmail.
Jim Hague <jim.hague@acm.org> [Fri, 09 Jan 2009 22:15:08 +0000] rev 7618
Bugzilla 2.18 and on use contrib/sendbugmail.pl, not processmail. During 2.17, Bugzilla ditched the old 'processmail' script. With 2.18 contrib/sendbugmail.pl arrived in its place. For notification emails to work properly, sendbugmail.pl requires as its second parameter the Bugzilla user who made the commit. Otherwise the user will not be recognised as the committer, and will receive notification emails about the commit regardless of their preference about being notified on their own commits. This parameter should be given to processmail also, but wasn't for historical reasons. Add new config with the local Bugzilla install directory, and provide defaults for the notify string which should work for most setups. Still permit notify string to be specified, and for backwards compatibility with any extant notify strings try first interpolating notify string with old-style single bug ID argument. Add new 2.18 support version to introduce sendbugmail.pl. In other words, this update should be backwards-compatible with existing installations, but offers simplified setup in most cases. And as a bonus Bugzilla notification emails will be dispatched correctly; notifiers will not receive an email unless configured to do so.
(0) -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 +30000 tip