Li Rongxiang

Li Rongxiang (simplified Chinese: 李荣祥; traditional Chinese: 李榮祥; pinyin: Lǐ Róngxiáng; born January 18, 1972 in Zhejiang) is a male javelin thrower from PR China. His personal best throw is 84.29 metres, achieved in May 2000 in Chengdu.

Achievements

Year Competition Venue Position Notes
Representing  China
1998 Asian Championships Fukuoka, Japan 2nd 77.48 m
Asian Games Bangkok, Thailand 3rd 78.57 m
1999 World Championships Seville, Spain 17th (q) 79.24 m
2001 East Asian Games Osaka, Japan 1st 81.55 m
World Championships Edmonton, Canada 9th 81.80 m
2002 Asian Championships Colombo, Sri Lanka 1st 82.75 m
World Cup Madrid, Spain 6th 78.12 m[1]
Asian Games Busan, South Korea 1st 82.21 m
2003 World Championships Paris, France 10th 78.24 m
Asian Championships Manila, Philippines 1st 79.25 m
Afro-Asian Games Hyderabad, India 2nd 79.01 m
2004 Olympic Games Athens, Greece 15th (q) 79.94 m
2005 World Championships Helsinki, Finland 18th (q) 74.95 m
Asian Championships Incheon, South Korea 1st 74.95 m
East Asian Games Macau 1st 79.75 m
2006 Asian Games Doha, Qatar 3rd 76.13 m

Seasonal bests by year

  • 1991 - 79.30
  • 1998 - 81.81
  • 1999 - 82.72
  • 2000 - 84.29
  • 2001 - 81.80
  • 2002 - 82.75
  • 2003 - 81.76
  • 2004 - 83.32
  • 2005 - 81.61
  • 2006 - 79.96
gollark: This is why you should use osmarks.tk osmarksbrowser.
gollark: Try NodeOS!
gollark: Or Great Information Transfer.
gollark: Git stands for GIT Is Tremendous.
gollark: The stages of git clone are: Receive a "pack" file of all the objects in the repo database Create an index file for the received pack Check out the head revision (for a non-bare repo, obviously)"Resolving deltas" is the message shown for the second stage, indexing the pack file ("git index-pack").Pack files do not have the actual object IDs in them, only the object content. So to determine what the object IDs are, git has to do a decompress+SHA1 of each object in the pack to produce the object ID, which is then written into the index file.An object in a pack file may be stored as a delta i.e. a sequence of changes to make to some other object. In this case, git needs to retrieve the base object, apply the commands and SHA1 the result. The base object itself might have to be derived by applying a sequence of delta commands. (Even though in the case of a clone, the base object will have been encountered already, there is a limit to how many manufactured objects are cached in memory).In summary, the "resolving deltas" stage involves decompressing and checksumming the entire repo database, which not surprisingly takes quite a long time. Presumably decompressing and calculating SHA1s actually takes more time than applying the delta commands.In the case of a subsequent fetch, the received pack file may contain references (as delta object bases) to other objects that the receiving git is expected to already have. In this case, the receiving git actually rewrites the received pack file to include any such referenced objects, so that any stored pack file is self-sufficient. This might be where the message "resolving deltas" originated.

References

  1. Representing Asia.



This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.