On Mon, 2012-12-10 at 11:02 -0800, Greg Kroah-Hartman wrote: > On Mon, Dec 10, 2012 at 01:47:44PM -0500, Steven Rostedt wrote: > > On Mon, 2012-12-10 at 12:35 -0500, Steven Rostedt wrote: > > > > > I have a crontab that updates these every night with a 'git remote > > > update' and once a week they do a 'git gc' on these repos. I notice the > > > above issues after the git gc. > > > > Looking at my script that does the git gc, it runs: > > > > git gc --aggressive > > > > on the stable.git tree. I wonder if that made a difference.
I know we're beating a dead horse here, but it would be interesting to know where the corruption came from. > > I think 'git gc' might have cause the problem, as it looks like it > pruned branches that you hadn't accessed in a long time, so it cleaned > them up. That's a scary thought... git gc will just prune stuff you haven't used in a while? I hope that's not the case. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
