On Fri, Jan 05, 2018 at 11:36:39AM -0800, Junio C Hamano wrote: > Jeff King <peff@xxxxxxxx> writes: > > > The problem is that I was bisecting an unrelated change in old code, and > > I built a commit which predates f98f8cbac0 (Ship sample hooks with .sample > > suffix, 2008-06-24). That wrote a bare "update" file into templates/blt > > (without the ".sample" suffix). After that, the cruft is forever in my > > build directory until I "git clean -x". > > > > The t5523 script tries to run "git push --quiet" and make sure that it > > produces no output, but with this setup it produces a round of "hint" > > lines (actually, they come from receive-pack on the remote end but still > > end up on stderr). > > > > So that raises a few interesting questions to me: > > > > 1. Should receive-pack generate these hints? They get propagated by > > the client, but there's a reasonable chance that the user can't > > actually fix the situation. > > True. The user could tell the server operator to rename them or > remove them because they are not doing anything useful, but then > as long as everybody knows they are not doing anything, it is OK > to leave that sleeping dog lie, as they are not doing anything > harmful anyway. > > That brings us one step further back to question if the hints are > useful in the first place, though ;-). Yes, that last paragraph definitely crossed my mind. Do we have an opinion on doing anything here? (E.g., declaring the hints not worth the trouble and reverting them versus just living with it)? -Peff
