From: Christopher Li <sparse@chrisli.org>
To: Mitesh Shah <mshah@teja.com>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: How do I get the latest sparse?
Date: Mon, 15 Jan 2007 16:17:35 -0800 [thread overview]
Message-ID: <20070116001735.GA12002@chrisli.org> (raw)
In-Reply-To: <AKEOJDDJLNPHDAKOMMBHCEGHCPAA.mshah@teja.com>
That is the same git repository I am pulling from. There is not
much update recently. I assume it is the Christmas/New Year holidays.
Don't worry, Josh will get back to us.
Chris
On Mon, Jan 15, 2007 at 03:48:26PM -0800, Mitesh Shah wrote:
> Hi,
>
> How do I get the latest version of sparse? The git repository from the
> sparse home page
> (http://kernel.org/pub/linux/kernel/people/josh/sparse/) does not show
> any update since Dec 05, 2006, while I see few patched submitted after
> that.
>
> Also the latest tarball URL gives me a version which is not updated
> since Nov 06
> (http://www.codemonkey.org.uk/projects/git-snapshots/sparse/sparse-lates
> t.tar.gz)
>
> Is there something I am missing?
>
> Thanks,
>
> -Mitesh
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-01-16 0:40 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 [this message]
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
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=20070116001735.GA12002@chrisli.org \
--to=sparse@chrisli.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.