Skip to content
Snippets Groups Projects
Commit a4c26918 authored by Siddharth Agarwal's avatar Siddharth Agarwal
Browse files

debugmergestate: explain why we create mergestate objects directly

We would normally use the read() constructor, but in this case it's fine
because
- we implement our own reading layer, so the extra parsing done by
   read() is unnecessary
- read() can raise an exception for unsupported merge state records,
   but here we'd like to handle that separately
- debugmergestate needs to be privy to mergestate internals anyway
parent 487cca1b
No related branches found
No related tags found
Loading
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment