All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zygmunt Ptak <zygmuntptak@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Clone source code recursively
Date: Thu, 25 Aug 2016 12:39:05 +0200	[thread overview]
Message-ID: <CAMkMO5=T9OtnDD-5Y8qu6ViAx=Cedze3WNmUus=_QiT=n+7vZw@mail.gmail.com> (raw)
In-Reply-To: <20160825101714.4cb710e9@free-electrons.com>

Hi,

> What do you call "recursively"? Are you talking about also fetching
submodules?
Exactly.

Thank you for information.
About nightly manual, yeah I saw that from Arnout email.

Regards
Zygmunt

2016-08-25 10:17 GMT+02:00 Thomas Petazzoni <
thomas.petazzoni@free-electrons.com>:

> Hello,
>
> On Thu, 25 Aug 2016 01:31:41 +0200, Zygmunt Ptak wrote:
>
> > I can't find how can I clone code recursively from git repository.
> > Is it possible at all?
>
> What do you call "recursively"? Are you talking about also fetching
> submodules? If that's what you're talking about, we recently added
> support for that:
>
>   https://git.buildroot.org/buildroot/commit/package/pkg-generic.mk?id=
> ec3e057f79117d851c37f19316a3b9b5e2470550
>
> You just need to add:
>
>   FOO_GIT_SUBMODULES = YES
>
> in your package .mk file.
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160825/b93eb554/attachment.html>

      reply	other threads:[~2016-08-25 10:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24 23:31 [Buildroot] Clone source code recursively Zygmunt Ptak
2016-08-25  7:41 ` Yann E. MORIN
2016-08-25  8:17 ` Thomas Petazzoni
2016-08-25 10:39   ` Zygmunt Ptak [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='CAMkMO5=T9OtnDD-5Y8qu6ViAx=Cedze3WNmUus=_QiT=n+7vZw@mail.gmail.com' \
    --to=zygmuntptak@gmail.com \
    --cc=buildroot@busybox.net \
    /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.