From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-browser] [PATCH 2/2] chromium, cef: fetch chromium source from git
Date: Thu, 28 May 2015 09:14:58 +0200 [thread overview]
Message-ID: <20150528071458.GA2383@jama> (raw)
In-Reply-To: <CAAzKXngfXaq4B87iQQXY0b-dxkncf8ROsYg4z0TnQFM5wNgxBw@mail.gmail.com>
On Thu, May 28, 2015 at 09:09:24AM +0200, Zoltan Kuscsik wrote:
> On 28 May 2015 at 02:56, Khem Raj <raj.khem@gmail.com> wrote:
> > >
> > > +do_fetch_chromium_source_from_git() {
> > > + cd ${S}
> > > + export PATH=${WORKDIR}/depot_tools:"$PATH"
> > > +
> > > + # Note: --deps-file needs to set to .DEPS.git for syncing to old
> > > + # chromium versions
> > > + gclient config ${CHROMIUM_SRC_GIT_URL} --deps-file=".DEPS.git"
> > > +
> > > + # Runhooks is disabled. Running the hooks will trigger the
> > > + # gyp_chromium command replaced with cef_create_projects.sh by
> > > + # cef3.
> > > +
> > > + gclient sync -f --nohooks --revision src@${CHROMIUM_SRC_GIT_COMMIT}
> > > +
> > > + # We need the lastchange hook to generate the LASTCHANGE revision info
> > > + # file.
> > > +
> > > + python src/build/util/lastchange.py -o src/build/util/LASTCHANGE
> > > +}
> >
> >
> > small nit. formatting is not correct for this shell function.
> >
>
> Z: Could you explain this in more details?
Use 4 spaces for indentation (everywhere).
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2015-05-28 7:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 17:37 [meta-browser] [PATCH 2/2] chromium, cef: fetch chromium source from git Zoltan Kuscsik
2015-05-28 0:56 ` Khem Raj
2015-05-28 7:09 ` Zoltan Kuscsik
2015-05-28 7:14 ` Martin Jansa [this message]
2015-06-03 19:26 ` Zoltan Kuscsik
2015-06-03 19:50 ` Khem Raj
2015-06-03 19:47 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2015-05-27 17:35 Zoltan Kuscsik
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=20150528071458.GA2383@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.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