From: Vikrampal <vikram.pal@samsung.com>
To: 'Andrei Emeltchenko' <andrei.emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, cpgs@samsung.com
Subject: RE: Android AOSP source tree downloading fails
Date: Tue, 17 Jun 2014 18:11:29 +0530 [thread overview]
Message-ID: <015801cf8a29$8660b250$932216f0$@samsung.com> (raw)
In-Reply-To: <20140617114548.GB621@aemeltch-MOBL1>
Hi Andrei,
>-----Original Message-----
>From: Andrei Emeltchenko [mailto:andrei.emeltchenko.news@gmail.com]
>Sent: Tuesday, June 17, 2014 5:16 PM
>To: Vikrampal
>Cc: linux-bluetooth@vger.kernel.org; cpgs@samsung.com
>Subject: Re: Android AOSP source tree downloading fails
>
>Hi Vikram,
>
>On Tue, Jun 17, 2014 at 04:59:28PM +0530, Vikrampal wrote:
>> Hi,
>>
>> I'm trying to download full Android AOSP source tree. I tried 2 methods:
>> 1) repo init -u https://code.google.com/p/aosp-bluez.platform-manifest
>> -b kitkat
>> repo sync
>> error: Exited sync due to fetch errors
>
>Which project it cannot fetch?
>
>Best regards
>Andrei Emeltchenko
platform/packages/apps/PackageInstaller
Regards,
Vikram
>>
>> 2) git clone https://code.google.com/p/aosp-bluez.platform-manifest
>> Warning: remote HEAD refers to nonexistent ref, unable to checkout
>>
>> Both the above methods failed.
>>
>> Please help me in downloading it. Thanks!
>>
>> Regards,
>> Vikram
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-bluetooth" in the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-06-17 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 11:29 Android AOSP source tree downloading fails Vikrampal
2014-06-17 11:45 ` Andrei Emeltchenko
2014-06-17 12:41 ` Vikrampal [this message]
2014-06-17 12:45 ` 'Andrei Emeltchenko'
2014-06-18 6:57 ` Vikrampal
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='015801cf8a29$8660b250$932216f0$@samsung.com' \
--to=vikram.pal@samsung.com \
--cc=andrei.emeltchenko.news@gmail.com \
--cc=cpgs@samsung.com \
--cc=linux-bluetooth@vger.kernel.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