Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: "Hennerich, Michael" <Michael.Hennerich@analog.com>
Cc: Bill Gatliff <bgat@billgatliff.com>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: Latest git tree for linux-iio?
Date: Wed, 23 Feb 2011 11:00:29 +0000	[thread overview]
Message-ID: <4D64E8CD.2080702@cam.ac.uk> (raw)
In-Reply-To: <544AC56F16B56944AEC3BD4E3D59177133FA3CCB43@LIMKCMBX1.ad.analog.com>

On 02/23/11 09:44, Hennerich, Michael wrote:
> Bill Gatliff wrote on 2011-02-23:
>> Guys:
>>
>>
>> Is there a recent git tree somewhere for the linux-iio framework?  The
>> one under jic23 on git.kernel.org shows an age of three months, and
>> doesn't seem to have a Documentation/iio directory either--- which
>> makes me thing it's the wrong stuff...
Good point. I've now killed that tree as we never actually bothered using
it.  In the end people were happy working against staging-next.

>>
>>
>> Thanks!
>>
>>
>> b.g.
> 
> Hi Bill,
> 
> All the development takes place in Greg's staging-next tree.
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging-2.6.git
> 
> Greetings,
> Michael
> 
> --
> Analog Devices GmbH      Wilhelm-Wagenfeld-Str. 6      80807 Muenchen
> Sitz der Gesellschaft: Muenchen; Registergericht: Muenchen HRB 40368; Geschaeftsfuehrer:Dr.Carsten Suckrow, Thomas Wessel, William A. Martin, Margaret Seif
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


      reply	other threads:[~2011-02-23 11:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23  5:04 Latest git tree for linux-iio? Bill Gatliff
2011-02-23  9:44 ` Hennerich, Michael
2011-02-23 11:00   ` Jonathan Cameron [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=4D64E8CD.2080702@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=Michael.Hennerich@analog.com \
    --cc=bgat@billgatliff.com \
    --cc=linux-iio@vger.kernel.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