From: robin <robinpv@iwavesystems.com>
To: openembedded-devel@lists.openembedded.org
Subject: git pull
Date: Tue, 19 Jan 2010 13:31:44 +0530 [thread overview]
Message-ID: <1263888104.2678.15.camel@ubuntu-desktop> (raw)
I am using the Openembedded for the beagleboard.
I had setup using below steps
export OETREE="${HOME}/OE"
mkdir -p ${OETREE} && cd ${OETREE}
git clone git://git.openembedded.org/openembedded.git openembedded
cd openembedded git checkout origin/stable/2009 -b stable/2009
cd ${OETREE}/openembedded
git pull
and then
bitbake beagleboard-demo-image
Now i wanted to update recipes folder.
git pull --rebase
It showed files which needs update. So i gave below command
git pull
But the recipes/ti folder is not updated with latest files,
which command needs to be used to update recipes directory ?
Robin
-------------------------------------------------------------------------------
DISCLAIMER: This e-mail and any attachment (s) is for authorised use by the
intended recipient (s) only. It may contain proprietary material, confidential
information and/or be subject to the legal privilege of iWave Systems
Technologies Private Limited. If you have received this message in error,
please notify the originator immediately. If you are not the intended
recipient, you are notified that you are strictly prohibited from retaining,
using, copying, alerting or disclosing the content of this message. Thank you
for your co-operation.
------------------------------------------------------------------------------
next reply other threads:[~2010-01-19 8:04 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 8:01 robin [this message]
2010-01-19 8:09 ` git pull robin
2010-01-19 18:37 ` Paul Wilson
2010-01-23 7:22 ` Khem Raj
2010-01-23 11:16 ` Bitbake build error on Fedora 12 x86 64-bit Elvis Dowson
2010-01-23 12:38 ` Elvis Dowson
2010-01-23 12:57 ` Holger Hans Peter Freyther
2010-01-23 13:24 ` Elvis Dowson
2010-01-23 14:51 ` Paul Menzel
2010-01-23 19:40 ` Elvis Dowson
2010-01-23 16:38 ` Holger Hans Peter Freyther
2010-01-24 13:50 ` Robert P. J. Day
2010-01-24 15:10 ` Holger Hans Peter Freyther
2010-01-24 15:34 ` Robert P. J. Day
2010-01-25 2:45 ` Holger Hans Peter Freyther
2010-01-25 11:49 ` Robert P. J. Day
2010-01-25 12:15 ` Koen Kooi
2010-01-25 12:35 ` Robert P. J. Day
2010-01-23 12:39 ` Graeme Gregory
2010-01-27 16:54 ` Elvis Dowson
2010-01-19 20:13 ` git pull Bjørn Forsman
2010-05-17 21:51 matteo brutti
2010-05-18 16:31 ` Nicolas Sebrecht
2010-05-19 11:03 ` hasen j
2012-04-12 14:47 GIT pull cvalusek
2012-04-12 15:03 ` Matthieu Moy
2012-04-12 15:07 ` Michael Witten
2012-04-12 16:58 ` Johannes Sixt
2012-04-12 17:29 ` cvalusek
2017-11-13 23:11 git pull Tobin C. Harding
2017-11-14 11:05 ` Greg Kroah-Hartman
2017-11-14 11:05 ` Greg Kroah-Hartman
2017-11-14 12:00 ` Ulf Hansson
2017-11-14 12:00 ` Ulf Hansson
2017-11-14 12:09 ` Greg Kroah-Hartman
2017-11-14 12:09 ` Greg Kroah-Hartman
2017-11-14 18:04 ` Linus Torvalds
2017-11-14 18:04 ` Linus Torvalds
2017-11-14 21:33 ` Tobin C. Harding
2017-11-14 21:33 ` Tobin C. Harding
2017-11-14 21:46 ` Linus Torvalds
2017-11-14 21:46 ` Linus Torvalds
2017-11-15 10:51 ` Michael Ellerman
2017-11-15 10:51 ` Michael Ellerman
2017-11-16 20:36 ` Linus Torvalds
2017-11-16 20:36 ` Linus Torvalds
2017-11-20 5:37 ` Junio C Hamano
2017-11-20 6:04 ` Linus Torvalds
2017-11-14 21:42 ` Tobin C. Harding
2017-11-14 21:42 ` Tobin C. Harding
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=1263888104.2678.15.camel@ubuntu-desktop \
--to=robinpv@iwavesystems.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 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.