Hi, Mitchell Blank Jr wrote: > Is it really hard to just make it purely time-based (git-rev-list > --max-age)? Think of if Linus is merging with a lot of people and then > pushes the results to the master repository -- suddenly there's, say, > 400 new commits since the last time my aggregator checked 2 hours ago.
Think of Linus merging a bunch of trees with 1-month old commits, all of which you'd miss that way. IMHO, you definitely need a static file for RSS -- do a git-rev-list between HEAD and HEAD-as-of-the-last-time-you-generated-the-RSS, concatenate with the old RSS, then trim appropriately. -- Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED] Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de - - You judge the acts of others only by their intentions. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html