tags 497687 + upstream severity 497687 important thanks Hi Mark,
Mark Brown wrote: > When git gui starts it does a check to see how many loose objects are in > the repository and displays a warning if this is over a certain number, > offering to do a gc. Since I track trees like linux-next that are > rebased and do a lot of local rebases myself I constantly run with a > large number of unpacked objects in my tree which won't be packed by gc > and hang around due to reflog and aging, meaning that the warning > constantly goes off even if I opt to run gc when prompted. Indeed, this is just stupid. I would like to investigate this soon (sorry to keep you waiting for so long!) and probably looking at the source will be enough, but just in case, it would be nice to know: - Can you still reproduce this with current git? - Would it be possible to tar up a .git directory with this problem somewhere I can look at it? Alternatively, is there a simple and reliable recipe for reproducing this? > Since the manual lists no way of disabling the warning and the garbage > collection which is suggested by the dialog doesn't actually resolve the > problem this is highly irritating. Yep. At the very least, it would be better UI design to provide a “don’t ask me again” check box! Thanks for the report, Jonathan -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
