Michael Haggerty
Michael Haggerty
Whew, that was a lot of comments. It's maybe a bit unfair of me to be so detailed after such a long time of inactivity. That's because I have been...
> @mhagger For what's it worth as an idle bystander - I'd love it if anyone gave such a detailed set of review notes on a pull request I made....
@dleen, @talios: I'm really sorry to be such a bottleneck, and given that I'm about to go on vacation for a few weeks I'm afraid things are not likely to...
I expect that this would be helpful to people using full imerge. Personally, I don't use that mode, partly because it takes so long and partly because the full mesh...
I'm no pygit2 expert, but I don't know of a reason that it couldn't be used instead of the Git command line client. But the installation complications pointed out by...
This should be easier to implement since the merge of #117.
The mojibake that you pasted, `Düring`, looks like the UTF-8 encoding of `ü`. Can you check somehow exactly what characters are in the commit? For example, run git cat-file commit...
`ü` in cp1252 is `0xFC`; in Unicode it is the same (`U+00FC`). The UTF-8 encoding of `U+00FC` is `0xC3 0xBC`. In cp1252 those bytes represent `ü`, the characters that you...
> It would be nice to have a `git imerge abort` command that did this automatically. Yes, that would be very nice. > I could take a stab at this,...
It sounds like you were using `imerge` correctly. Yes, there must have been a byte `\xe2` somewhere in the commit that it was trying to process, probably in either the...