From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: John Daiker <daikerjohn@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Ath5k compile error in wireless-2.6.git
Date: Tue, 16 Oct 2007 13:01:55 -0400 [thread overview]
Message-ID: <20071016170155.GB5677@tuxdriver.com> (raw)
In-Reply-To: <43e72e890710160914g2caa998cpd7bbb058fd064372@mail.gmail.com>
On Tue, Oct 16, 2007 at 12:14:17PM -0400, Luis R. Rodriguez wrote:
> On 10/15/07, John W. Linville <linville@tuxdriver.com> wrote:
> > On Mon, Oct 15, 2007 at 07:46:01PM -0400, John W. Linville wrote:
> > > On Mon, Oct 15, 2007 at 03:38:02PM -0700, John Daiker wrote:
> > > > John,
> > > >
> > > > I just checked out the wireless-2.6.git tree from Kernel.org to test the
> > > > new ath5k driver. I get the following compile error on a 'vanilla'
> > > > git-clone.
> > >
> > > Please use the 'everything' branch for development.
> > >
> > > git checkout everything
>
> Approach 1
>
> > Hmmm...maybe this instead:
> >
> > git checkout -b everything origin/everything
>
> Approach 2
>
> What's fun is that the above is approach 1 is actually necessary on
> PowerPC. It seems git for powerpc still uses the old branch stuff. For
> example I can't use approach 2. I'll add this to the wiki for ath5k,
> just a head up in case there's some PowerPC users out there.
I think this has more to do with the git version (i.e. release) than
the architecture. "Approach 1" worked everywhere for a long time,
while I only became aware of "Approach 2" a few months ago.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-10-16 17:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 22:38 Ath5k compile error in wireless-2.6.git John Daiker
2007-10-15 23:46 ` John W. Linville
2007-10-15 23:47 ` John W. Linville
2007-10-16 16:14 ` Luis R. Rodriguez
2007-10-16 17:01 ` John W. Linville [this message]
2007-10-16 18:05 ` Luis R. Rodriguez
2007-10-16 18:17 ` John W. Linville
2007-10-16 0:27 ` Luis R. Rodriguez
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=20071016170155.GB5677@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=daikerjohn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.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.