pull: properly distinguish remote messages from progress
The previous logic was kind of weird. It parsed the messages rather thoroughly, but ignored a crucial distinction: * Anything that ends with a newline is most likely a remote message. * Anything that ends with a carriage return is most likely a progress message. * Lines ending with newline always flush a progress session. Most things ending with newline are interesting, but we explicitly disregard the “totals” stuff. Things ending with carriage return are either progress, or at least something we shouldn't print.
parent
2a755587
No related branches found
No related tags found
Pipeline #30078 failed
Stage: images
Stage: current
Stage: compat
Stage: upcoming
Stage: archives
Stage: .post
Showing
- hggit/git_handler.py 54 additions, 38 deletionshggit/git_handler.py
- tests/hghave.py 1 addition, 0 deletionstests/hghave.py
- tests/test-push-to-head.t 39 additions, 0 deletionstests/test-push-to-head.t
- tests/test-serve-ci.t 2 additions, 0 deletionstests/test-serve-ci.t
- tests/test-serve-dulwich.t 4 additions, 4 deletionstests/test-serve-dulwich.t
- tests/test-serve-git.t 0 additions, 5 deletionstests/test-serve-git.t
Loading
Please register or sign in to comment