From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "Luis R. Rodriguez" <mcgrof@frijolero.org>, backports@vger.kernel.org
Subject: Re: Problem with backports git repo
Date: Tue, 28 May 2013 21:43:09 +0200 [thread overview]
Message-ID: <1369770189.8548.20.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1369769122.8548.7.camel@jlt4.sipsolutions.net> (sfid-20130528_212531_921012_9500F06E)
On Tue, 2013-05-28 at 21:25 +0200, Johannes Berg wrote:
> Hi Larry,
>
> > I just used 'git clone' to get a fresh copy of the repo. When I try 'make
> > menuconfig', I get the following error:
> >
> > finger@larrylap:~/backports/backport> make menuconfig
>
> The docs haven't been updated, but this is just the skeleton, you're not
> supposed to run anything in there. Go to the top-level first, and run
Oh, n/m me, it seems this was just an accidental resend of your previous
mail?
johannes
next prev parent reply other threads:[~2013-05-28 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 19:17 Problem with backports git repo Larry Finger
2013-05-28 19:25 ` Johannes Berg
2013-05-28 19:43 ` Johannes Berg [this message]
2013-05-28 19:56 ` Larry Finger
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=1369770189.8548.20.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=backports@vger.kernel.org \
--cc=mcgrof@frijolero.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