From: Mitchell Blank Jr <mitch@sfgoth•com>
To: Kay Sievers <kay.sievers@vrfy•org>
Cc: Ian Campbell <ijc@hellion•org.uk>, git@vger•kernel.org
Subject: Re: gitweb - feature request
Date: Fri, 12 Aug 2005 14:16:00 -0700 [thread overview]
Message-ID: <20050812211600.GA61428@gaz.sfgoth.com> (raw)
In-Reply-To: <20050812203322.GB9696@vrfy.org>
Kay Sievers wrote:
> It's 30 now and up to 150 if they are not older than 48 hours.
> We can change the numbers, if you hava a better idea...
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.
> For now it just lists all changed files to the log message, similar to the
> "commit" view. Is that ok, or do we really need the diffstat,
It looks great, thanks! diffstat would be slightly nicer but not a big
deal.
> It may be
> a bit expensive to generate it for all the commits with every RSS request...
Well if the RSS feed's popularity takes off you'll probably want to *not*
generate it every time and instead serve it from a static file. This can
be as simple as a Makefile like:
commits.rss: $(GITDIR)/refs/heads/master
/path/to/myperlscript.pl $(GITDIR) > commits.rss.NEW && chmod 444 commits.rss.NEW && mv commits.rss.NEW commits.rss
and then call "make -C /my/rss/dir -s -f /path/to/mymakefile.mk" from cron
every minute.
Serving the rss from a static file has the big advantage that a well-behaved
aggregator will only request it if the modification date changed which saves
everyone bandwidth.
-Mitch
next prev parent reply other threads:[~2005-08-12 21:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 19:31 gitweb - feature request Sam Ravnborg
2005-08-09 19:58 ` Kay Sievers
2005-08-09 20:18 ` Sam Ravnborg
2005-08-09 20:27 ` Johannes Schindelin
2005-08-09 20:43 ` Sam Ravnborg
2005-08-09 20:51 ` John Benes
2005-08-09 21:09 ` Kay Sievers
2005-08-09 21:53 ` Linus Torvalds
2005-08-10 0:11 ` Kay Sievers
2005-08-10 0:19 ` Linus Torvalds
2005-08-09 21:14 ` Kay Sievers
2005-08-10 2:00 ` Kay Sievers
2005-08-10 5:18 ` Sam Ravnborg
2005-08-10 5:53 ` Ian Campbell
2005-08-10 8:31 ` Mitchell Blank Jr
2005-08-12 20:33 ` Kay Sievers
2005-08-12 21:16 ` Mitchell Blank Jr [this message]
2005-08-13 4:13 ` Matthias Urlichs
2005-08-12 20:27 ` Kay Sievers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050812211600.GA61428@gaz.sfgoth.com \
--to=mitch@sfgoth$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=ijc@hellion$(echo .)org.uk \
--cc=kay.sievers@vrfy$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox