From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Building minimal-image with kernel24
Date: Thu, 11 Dec 2008 11:18:28 -0500 [thread overview]
Message-ID: <49413D54.5090908@balister.org> (raw)
In-Reply-To: <f96d234e0812110751v47a0425ck15adb418fd4ae94a@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1632 bytes --]
Cliff Brake wrote:
> On Thu, Dec 11, 2008 at 12:08 AM, Joshua Lamorie <jpl@xiphos.ca> wrote:
>> Gidday there,
>>
>> Sorry for this simple question, but I've been using subversion up to now, and I can't figure out how to use git to checkout/pull/clone the documentation. I can see the results of ...
>>
>> git-ls-remote --heads git://git.openembedded.net/openembedded.git refs/heads/org.openembedded.documentation
>>
>> Then, inside the openembedded repository that I cloned with
>>
>> git clone git://git.openemebbeded.net/openembedded.git
>>
>> I can see the other branches with
>>
>> [jpl@megatron openembedded]$ git branch -r
>>
>> However, as suggested in http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#examining-remote-branches, I do a checkout and I get the following.
>>
>> [jpl@megatron openembedded]$ git checkout -b documentation origin/org.openembedded.documentation
>> fatal: Entry 'packages/tinylogin/tinylogin_1.4.bb' not uptodate. Cannot merge.
>>
>> There is an error in that .bb file (I just added a patch to bugzilla) but shouldn't I be able to get this branch without dealing with the uncommited changes to that file?
>
> You will need to commit your local changes to a temp branch first.
>
> git checkout -b myfixes org.openembedded.dev
> git add ...
> git commit
>
> Now that you have no local changes, you can check out the doc
You can also use git stash to save local changes. Then can update your
working copy and re-apply the changes from the "stash". This avoids the
need to commit stuff you are not certain about.
Philip
>
> Cliff
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
prev parent reply other threads:[~2008-12-11 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 21:40 Building minimal-image with kernel24 Joshua Lamorie
2008-12-10 22:27 ` Cliff Brake
2008-12-11 5:08 ` Joshua Lamorie
2008-12-11 15:51 ` Cliff Brake
2008-12-11 16:18 ` Philip Balister [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=49413D54.5090908@balister.org \
--to=philip@balister.org \
--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.