Skip to contentSkip to conversation

Stale references in the u-boot-samsung repo

U-Boot Albert ARIBAUD 3 participants 4 messages Dec 6, 2013

lore
Share & tools
lore
#0 lore raw

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!

Amicalement,

Signature · 1 line
Albert.
#1 lore raw

Hi Albert,

Quoted 13 lines · Albert ARIBAUD

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!

Quoted 8 lines

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!

Quoted 2 lines

Amicalement,

Thanks,
Minkyu Kang.

#2 lore raw

Hi Minkyu,

Quoted 19 lines · Minkyu Kang

Hi Albert,

Quoted 16 lines · Albert ARIBAUD

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!

Quoted 7 lines
Quoted 5 lines

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.

Quoted 2 lines

Thanks,
Minkyu Kang.

Amicalement,

Signature · 1 line
Albert.
#3 lore raw
In reply to Albert ARIBAUD
Quoted 13 lines · Albert ARIBAUD

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!

Quoted 7 lines

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!

Note that these aren't a u-boot-samsung specific problem, I see this too for master, but have just ignored it.

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20131206/9560555c/attachment.pgp>