All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: git clone of linux kernel provides only compressed pack files
Date: Fri, 20 Jan 2012 14:13:32 -0500	[thread overview]
Message-ID: <20120120191332.GB17875@kroah.com> (raw)
In-Reply-To: <CAJKgH8DcR87AVU_9_PyT7NpCqjajY0iQNoXdb+-pKP63UcdtZA@mail.gmail.com>

On Sat, Jan 21, 2012 at 12:06:08AM +0530, Manavendra Nath Manav wrote:
> On Fri, Jan 20, 2012 at 6:55 PM, Mirco Tischler <mt-ml@gmx.de> wrote:
> 
> **snip**
> > You just need to do git checkout master after the git clone. This
> > gives you the version the master branch in the stable repo points to
> > at the time of the cloning.
> > To update your local master branch later, just do git pull.
> >
> > git unpack-objects is usually not directly needed by users. It's
> > called by git internally though.
> >
> > Mirco
> 
> Thanks Mirco, after doing git checkout and git pull on cloned Linux
> git repo, I can see all the Linux source files. The problem got
> resolved for Linux tree but for android repository, I am still facing
> issues.

That's different, you need to check out the specific android kernel repo
you want to use, by the branch name.

The android kernel tree is "wierd" that way, try doing this:
	git checkout android-3.0
and you should be fine.

Even better yet, do this:
	git checkout -t -b android-3.0 origin/android-3.0

which creates a "tracking branch" for this branch of their kernel tree,
which will let you handle things when they update it in the future to
newer releases.

Hope this helps,

greg k-h

  reply	other threads:[~2012-01-20 19:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-20 13:08 git clone of linux kernel provides only compressed pack files Manavendra Nath Manav
2012-01-20 13:25 ` Mirco Tischler
2012-01-20 18:36   ` Manavendra Nath Manav
2012-01-20 19:13     ` Greg KH [this message]
2012-01-20 19:50       ` Manavendra Nath Manav
2012-01-20 15:42 ` Jonathan Neuschäfer

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=20120120191332.GB17875@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 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.