Thread (5 messages) flat view 5 messages, 3 authors, 2016-06-16

Re: Mark remote `gc --auto` error messages

From: Junio C Hamano <hidden>
Date: 2016-06-16 02:19:42

On Thu, Jun 2, 2016 at 1:06 PM, Lukas Fleischer [off-list ref] wrote:
On Thu, 02 Jun 2016 at 21:33:33, Junio C Hamano wrote:
quoted
Lukas Fleischer [off-list ref] writes:
quoted
When running `git push`, it might occur that error messages are
transferred from the server to the client. While most messages (those
explicitly sent on sideband 2) are prefixed with "remote:", it seems
that error messages printed during the automatic householding performed
by git-gc(1) are displayed without any additional decoration. Thus, such
messages can easily be misinterpreted as git-gc failing locally, see [1]
for an actual example of where that happened.
Sounds like a sensible goal to me.
What exactly are you referring to (you only quoted the introduction)?
Do you think we should fix the git-gc issue but keep the general
behavior of printing messages unaltered? Do you think it would be
worthwhile to make server messages distinguishable in general?
The latter, which I think was what your implementation was attempting to do
if I read it correctly.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help