Skip to contentSkip to conversation

git setlocalversion

U-Boot Derek Ou 2 participants 2 messages Feb 12, 2009

lore
Share & tools
lore

Derek Ou

author
#0 lore raw

Our company uses svn for the source code management but I use git locally to track
my development. When I build U-boot, it always complains about "fatal:
cannot
describe" the SHA1 # of HEAD. It goes back to line 16 of tools/setlocalversion.

I know that the error will go away when I tag my git HEAD. But what is the philosophy of this setlocalversion? Should I always tag the top commit of my
git tree to maintain a clean U_BOOT_VERSION define?

Derek

#1 lore raw
Quoted 11 lines · On Thursday 12 February 2009 17:30:24 Derek Ou wrote:

Our company uses svn for the source code management but I use git locally to track
my development. When I build U-boot, it always complains about "fatal:
cannot
describe" the SHA1 # of HEAD. It goes back to line 16 of tools/setlocalversion.

I know that the error will go away when I tag my git HEAD. But what is the philosophy of this setlocalversion? Should I always tag the top commit of my
git tree to maintain a clean U_BOOT_VERSION define?

it's to provide a simple way of getting the "current" git tree into the u-boot build. it doesnt always work. i recall fixing this once locally (as i was using git-svn for a u-boot svn repo), but i dont recall exactly how i did it. -mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090212/fe2f55d1/attachment.pgp