All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jaggi, Manish" <Manish.Jaggi@caviumnetworks.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream
Date: Mon, 25 Apr 2016 16:10:16 +0000	[thread overview]
Message-ID: <BY1PR0701MB159480B842DF78C33DA2A161E1620@BY1PR0701MB1594.namprd07.prod.outlook.com> (raw)
In-Reply-To: <CAJTo0LY9Vtas26+M_Zq2fzREkpqXLD-uNOtXpJbzN8_9it=1Pg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 895 bytes --]


________________________________
From: Burton, Ross <ross.burton@intel.com>
Sent: Monday, April 25, 2016 8:12 PM
To: Jaggi, Manish
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream


On 25 April 2016 at 14:30, Jaggi, Manish <Manish.Jaggi@caviumnetworks.com<mailto:Manish.Jaggi@caviumnetworks.com>> wrote:
It seems the revid / tag is not on any branch
git branch  --contains 2134d97aa3a7ce38bb51f933f2e20cafde371085
returns nothing.

How to fix this issue ?

You probably want to use git branch -r --contains 213... as otherwise git branch will only list local branches.  The web UI says that this commit exists on master though...

[Manish] Same output with -r.
Can you please share the link of web ui. As per the error it is not on master branch.


Ross

[-- Attachment #2: Type: text/html, Size: 2276 bytes --]

  reply	other threads:[~2016-04-25 16:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25 13:30 Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream Jaggi, Manish
2016-04-25 14:42 ` Burton, Ross
2016-04-25 16:10   ` Jaggi, Manish [this message]
2016-04-25 17:34     ` Bruce Ashfield
2016-04-26  1:05       ` Jaggi, Manish
2016-04-26  2:11         ` Bruce Ashfield
2016-04-26  7:32           ` Zhenhua Luo
2016-04-26  7:46             ` Jaggi, Manish

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=BY1PR0701MB159480B842DF78C33DA2A161E1620@BY1PR0701MB1594.namprd07.prod.outlook.com \
    --to=manish.jaggi@caviumnetworks.com \
    --cc=ross.burton@intel.com \
    --cc=yocto@yoctoproject.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.