From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Stale references in the u-boot-samsung repo
Date: Fri, 6 Dec 2013 17:41:11 +0100 [thread overview]
Message-ID: <20131206174111.7534a2c5@lilith> (raw)
In-Reply-To: <52A1AA8C.1060809@samsung.com>
Hi Minkyu,
On Fri, 06 Dec 2013 19:44:28 +0900, Minkyu Kang <mk7.kang@samsung.com>
wrote:
> Hi Albert,
>
> On 06/12/13 17:44, Albert ARIBAUD wrote:
> > Hi Minkyu,
> >
> > While fetching u-boot-samsung, I could see the following messages:
> >
> > remote: error: refs/remotes/origin/GPL-Cleanup does not point to a
> > valid object!
> >
> > remote: error: refs/remotes/origin/i.MX31 does not point to a valid
> > object!
> >
> > remote: error: refs/remotes/origin/lwmon5 does not point to a valid
> > object!
> >
> > remote: error: refs/remotes/origin/mkimage does not point to a valid
> > object!
> >
> > It looks like these branches that were pushed on the remote, then later
> > the commit to which they point was cleaned up.
> >
> > Can you fix this? Thanks in advance!
> >
>
> Please let me know how I can fix it!
For branches which you still need to publish and for which are correct
in your working repo, you can do a push as you would for master or
next, e.g.
git push [...] branchname:branchname
where branchname should be replaced (on both sides of the colon) with
the actual name of the branch you want to update.
For branches which you don't need to publish any more, you can remove
them on the Denx repo with:
git push [...] :branchname
where there is nothing on the left side of the colon, and branchname
is replaced with the actual name of the branch you want to remove.
> Thanks,
> Minkyu Kang.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-12-06 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 8:44 [U-Boot] Stale references in the u-boot-samsung repo Albert ARIBAUD
2013-12-06 10:44 ` Minkyu Kang
2013-12-06 16:41 ` Albert ARIBAUD [this message]
2013-12-06 16:57 ` Tom Rini
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=20131206174111.7534a2c5@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/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