From: David Woodhouse <dwmw2@infradead.org>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: linux-mtd@lists.infradead.org, Davide CASCONE <davide.cascone@st.com>
Subject: Re: latest patch download
Date: Mon, 22 May 2006 14:16:58 +0100 [thread overview]
Message-ID: <1148303818.12285.53.camel@pmac.infradead.org> (raw)
In-Reply-To: <1148302661.26156.8.camel@pim.off.vrfy.org>
On Mon, 2006-05-22 at 14:57 +0200, Kay Sievers wrote:
> How can we determine the "not anything new" state? :)
git-diff origin.. | wc -l
Oh, wait... _its_ version of 'origin' will of course still be older.
But if I just configure gitweb with a _static_ list of 'parent trees' to
use for the 'not anything new' state, that's fine. If the tree in
question is a strict subset of _any_ of the listed 'parent trees', then
it's not interesting.
We can probably do even better than that -- we can look at what's in
remotes/origin and use that instead.
Actually, half those trees don't have remotes/origin at the moment --
but that's easily fixed. I have to create the list of repositories with
a script _anyway_, because it has to go looking in users' ~/public_git
directories. So I suppose I can make that script _ignore_ any repos
without it.
Actually, I'd like to group repos in the display according to their
parent. So all the repos based on mtd-2.6.git would be together, all the
repos based on mtd-utils.git would be together, and then the ones
without a matching parent would be in another group.
We could even put the intended parent into the index.aux file so that
gitweb doesn't have to work that out for itself.
> Does sorting it by age doesn't do what you are looking for?
> http://git.infradead.org/?o=age
Hm, didn't know _that_ existed either. Is there documentation I haven't
been paying attention to?
--
dwmw2
prev parent reply other threads:[~2006-05-22 13:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 10:21 latest patch download Davide CASCONE
2006-05-22 11:57 ` David Woodhouse
2006-05-22 12:09 ` Kay Sievers
2006-05-22 12:49 ` David Woodhouse
2006-05-22 12:57 ` Kay Sievers
2006-05-22 13:16 ` David Woodhouse [this message]
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=1148303818.12285.53.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=davide.cascone@st.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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