Linux M68K Architecture development
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Rob Landley <rob@landley.net>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	linux-kernel@vger.kernel.org, dwmw2@infradead.org,
	linux-next@vger.kernel.org, linux-m68k@lists.linux-m68k.org
Subject: Re: make headers_install broken for ARCH=m68k in 2.6.29-rc7.
Date: Wed, 18 Mar 2009 15:34:43 +1000	[thread overview]
Message-ID: <49C087F3.3080507__49133.6115207106$1237354582$gmane$org@snapgear.com> (raw)
In-Reply-To: <200903172304.00157.rob@landley.net>

Hi Rob,

Rob Landley wrote:
> On Monday 16 March 2009 18:10:45 Greg Ungerer wrote:
>>>>    git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git
>>>> fix-includes
> ...
>> Did you get the "fix-includes" branch?
> 
> Quite possibly not.  (I'm not a git person.)
> 
> I did a "git clone git://blah fix-includes" of the branch you gave a URL to, 
> checked for tags and saw nothing particularly interesting, did a log -v and 
> exported an archive of the most recent commit, and built it.
> 
> (Just tried it again with the same result.)
> 
> What _should_ I have done?

The git clone you have done will just get the master branch,
and put it in a directory named fix-includes.

Which is ok, but you still won't have the "fix-includes" branch.
Do this after the clone:

   git pull 
git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git 
fix-includes

Regards
Greg


------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear, a McAfee Company                  PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com

  reply	other threads:[~2009-03-18  5:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200903120437.03837.rob@landley.net>
     [not found] ` <20090312210216.GB14205@uranus.ravnborg.org>
     [not found]   ` <10f740e80903121540i30fdaddr600ce21f4159530a@mail.gmail.com>
     [not found]     ` <200903122225.04560.rob@landley.net>
     [not found]       ` <49BA0599.6070206@snapgear.com>
     [not found]         ` <20090313082555.GA19045@uranus.ravnborg.org>
     [not found]           ` <10f740e80903130133r130b8713v690437f0f38eb0b8@mail.gmail.com>
     [not found]             ` <20090313085930.GA19274@uranus.ravnborg.org>
     [not found]               ` <49BA3B05.9020906@snapgear.com>
2009-03-13 12:14                 ` make headers_install broken for ARCH=m68k in 2.6.29-rc7 Geert Uytterhoeven
2009-03-16 12:40                   ` Greg Ungerer
     [not found]                   ` <49BE48B3.6060108@snapgear.com>
2009-03-16 20:20                     ` Rob Landley
     [not found]                     ` <200903161521.00036.rob@landley.net>
2009-03-16 22:08                       ` Geert Uytterhoeven
2009-03-16 23:09                         ` Greg Ungerer
2009-03-16 23:10                       ` Greg Ungerer
2009-03-18  4:03                         ` Rob Landley
2009-03-18  5:34                           ` Greg Ungerer [this message]
     [not found]                           ` <49C087F3.3080507@snapgear.com>
2009-03-18 18:12                             ` Rob Landley
     [not found]                             ` <200903181312.02047.rob@landley.net>
2009-03-18 23:53                               ` Greg Ungerer
2009-03-19  7:59                               ` Geert Uytterhoeven
2009-03-19  8:41                                 ` Rob Landley

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='49C087F3.3080507__49133.6115207106$1237354582$gmane$org@snapgear.com' \
    --to=gerg@snapgear.com \
    --cc=dwmw2@infradead.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=sam@ravnborg.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