Nguyễn Thái Ngọc Duy <pclouds@xxxxxxxxx> writes: > This gives users a chance to run gc explicitly elsewhere if they do not > want gc to run suddenly in current terminal. > > Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@xxxxxxxxx> As I am still in a cheerly holiday mood, let's be a bit philosophical, step back a bit and think. After this patch gets applied, will the users start feeling bothered by repeated "you will soon see auto-gc" messages and will want "you will soon start seeing the you will soon see auto-gc messages" warnings? And if the answer to that tongue-in-cheek question is no, what is the reason why the users will not find the messages disturbing, while loathing the auto-gc? I suspect that is because auto-gc takes long time, making the user wait, compared to the new message that may be noisy but quick. Perhaps the real cure for the disease is not to add the message but to make an auto-gc less painful, no? What are the things we could do to make auto-gc less painful? Are we doing something that is not necessary in auto-gc that takes time but that we can live without doing? It may be a better cure for the disease to force a full gc after operations that we know the users already know to take long time (e.g. a clone, a large fetch), so that the next auto-gc do not have to do much work. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html