- User Since
- Jun 29 2017, 11:25 AM (28 w, 5 d)
I think the frame details aren't important here, so making some lines optional
should be just fine.
Sun, Jan 14
Fri, Jan 12
Just for the record, explicit killdaemon isn't needed unless you want
to do something (e.g. checking server logs) after that. Daemons are
kill by the test runner.
FWIW, it might be good idea to move context._filterederror() to obsutil.py
because context.py is painfully big.
Thu, Jan 11
bytes() or "%d" is preferred. Can you send a follow up?
I think it's new feature. Which Rust version should we support?
Wed, Jan 10
Queued for stable. Thanks for fixing this issue.
Sun, Jan 7
Sat, Jan 6
Are you thinking that it may be useful if the function in my test case is instead a stand-alone script/binary?
Fri, Jan 5
Needs some warning since a hidden revision may be revived?
I'm drunk, but I'm sure this is good. Queued, thanks.
Suppose this is a kind of contrib code, I think it's good enough to accept.
Can you drop Cargo.lock file?
However, it is quite large and I suspect it will take a bit more effort to finish it.
Thu, Jan 4
We hold off incrementing the version of the "parsers" extension
because nothing in core relies on the new API yet.
Thu, Dec 28
Because we're now using a custom type and conforming to
a yet-to-be-formally-defined interface, there's nothing
preventing us from implementing a backed-by-C custom type
for revlog entries.
Queued, thanks. I've made asc/desc classes private as their constructor
behavior is weird.
Wed, Dec 27
Can you update the other callers which pass ['']?
Tue, Dec 26
FWIW, if the cache don't include "unhidden" revisions, maybe we don't
need new filter names like 'visible-hidden"?
Yep I agree, but I wanted be on the safe side to prevent unknown bugs by using the same filtername.