From: Randy Dunlap <rdunlap@xenotime.net>
To: Mitesh Shah <mshah@teja.com>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>, davej@codemonkey.org.uk
Subject: Re: How do I get the latest sparse?
Date: Mon, 15 Jan 2007 18:15:15 -0800 [thread overview]
Message-ID: <20070115181515.a2573235.rdunlap@xenotime.net> (raw)
In-Reply-To: <AKEOJDDJLNPHDAKOMMBHCEGJCPAA.mshah@teja.com>
On Mon, 15 Jan 2007 17:07:10 -0800 Mitesh Shah wrote:
> > http://www.codemonkey.org.uk/projects/git-snapshots/sparse/ says:
> >
> > [ ] sparse-2007-01-10.tar.gz 10-Jan-2007 23:01 169K
> > [ ] sparse-2007-01-11.tar.gz 11-Jan-2007 23:01 169K
> > [ ] sparse-2007-01-12.tar.gz 12-Jan-2007 23:01 169K
> > [ ] sparse-2007-01-13.tar.gz 13-Jan-2007 23:00 169K
> > [ ] sparse-2007-01-14.tar.gz 14-Jan-2007 23:00 169K
> > [ ] sparse-2007-01-15.tar.gz 15-Jan-2007 23:01 169K
> > [ ] sparse-2007-01-16.tar.gz 16-Jan-2007 00:01 169K
> > [ ] sparse-latest.tar.gz 16-Jan-2007 00:01 169K
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >
> > ---
> > ~Randy
> >
>
> Yes, but if you unzip and untar that file, you will see that the sources
> are not updated since Nov 6, 2006. So my guess is that the tar is being
> built everyday but the checkout is not happening from the correct source
> repository.
Oh, OK, thanks. We'll let the codemonkey know. :)
---
~Randy
next prev parent reply other threads:[~2007-01-16 2:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 23:48 How do I get the latest sparse? Mitesh Shah
2007-01-16 0:17 ` Christopher Li
2007-01-16 12:23 ` Josh Triplett
2007-01-17 1:49 ` Christopher Li
2007-01-17 5:41 ` Josh Triplett
2007-01-17 6:31 ` Christopher Li
2007-01-17 19:05 ` Sam Ravnborg
2007-01-17 20:03 ` Christopher Li
2007-01-16 0:59 ` Randy Dunlap
2007-01-16 1:07 ` Mitesh Shah
2007-01-16 2:15 ` Randy Dunlap [this message]
2007-01-16 3:16 ` Dave Jones
2007-01-16 12:14 ` Josh Triplett
2007-01-16 15:40 ` Mitesh Shah
2007-01-17 0:23 ` Dave Jones
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=20070115181515.a2573235.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=davej@codemonkey.org.uk \
--cc=linux-sparse@vger.kernel.org \
--cc=mshah@teja.com \
/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;
as well as URLs for NNTP newsgroup(s).