You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2010-05-15 03:19:35
- Acecero
- Member
- Registered: 2008-06-21
- Posts: 1,373
The recent Vim update.
I'm curious, is there a reason why the new vim package that just got pushed to extra has declared it got 2150 patches, while checking the actual amount was 432 patches?
Offline
#2 2010-05-15 03:23:40
- Allan
- Pacman
- From: Brisbane, AU
- Registered: 2007-06-09
- Posts: 11,672
- Website
Re: The recent Vim update.
The new vim package is built from hg so that it gets the updated vim runtime files which are difficult to get otherwise. 2150 is the hg revision.
Edit: that really is not quite right. We have a different version numbering that everyone else now....
Offline
#3 2010-05-15 10:55:28
- kazuo
- Member
- From: São Paulo/Brazil
- Registered: 2008-03-18
- Posts: 413
- Website
Re: The recent Vim update.
And is not best to use changeset ID to name commits in a mercurial repo? The rev number are inconsistent, are not? (sorry if I'm wrong...)
A revision number is a simple decimal number that corresponds with the ordering of commits in the local repository. It is important to understand that this ordering can change from machine to machine due to Mercurial's distributed, decentralized architecture.
Last edited by kazuo (2010-05-15 10:56:46)
Offline
#4 2010-05-15 11:02:35
- Allan
- Pacman
- From: Brisbane, AU
- Registered: 2007-06-09
- Posts: 11,672
- Website
Re: The recent Vim update.
It will change on local repos, but the order on the master repo is static.
Offline
Pages: 1