- Aug 12, 2010
-
-
Daniel Dumitriu authored
-
- Aug 24, 2010
-
-
Wagner Bruna authored
-
- Aug 21, 2010
-
-
Martin Geisler authored
-
Martin Geisler authored
-
- Aug 20, 2010
-
-
Paolo Giarrusso authored
-
Paolo Giarrusso authored
The translations were all random fuzzy strings, which can only do harm, so remove them. Moreover, given the status of revset (it seems mostly an internal undocumented module, and to understand it you need the source anyway), I prefer not to translate it for now.
-
Paolo Giarrusso authored
-
Paolo Giarrusso authored
Significant updates were performed - when translating something, I tried to choose a term and use it consistently everywhere possible, so here I translated a lot of messages. Additionally, I use the mq extension a lot, and now I am using the translation, so I will be able to translate it better.
-
Paolo Giarrusso authored
-
Paolo Giarrusso authored
This patch follows the fix on the translation of [OPTION]... with other needed updates on the same class of messages.
-
Paolo Giarrusso authored
Since [OPTION]... is intended to mean more options, it was translated in Italian as plural. However the plural is conveyed by `...', so switch to the singular. This was also useful because for the '-o OPT' extdiff option, I have to translate `OPT' as a singular.
-
Paolo Giarrusso authored
The problem was introduced already in revision 9f9137cd83f5 by the original Italian translator, according to logs. This might be due to a bug in the program he used, "Lokalize 0.3", or maybe not - some accented characters exist also in that commit.
-
Paolo Giarrusso authored
-
Paolo Giarrusso authored
-
- Aug 21, 2010
-
-
Wagner Bruna authored
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
- Aug 20, 2010
-
-
Matt Mackall authored
-
Matt Mackall authored
-
Adrian Buehlmann authored
-
- Aug 19, 2010
-
-
Matt Mackall authored
-
Matt Mackall authored
-
- Aug 13, 2010
-
-
Vishakh H authored
While reading changegroup if a node with missing parents is encountered, we add a punched entry in the index with null parents for the missing parent node.
-
Vishakh H authored
The full revision is sent if the first parent, against which diff is calculated, is missing at remote. This happens in the case of shallow clones.
-
- Aug 19, 2010
-
-
Benoit Boissinot authored
-
Benoit Boissinot authored
-
Benoit Boissinot authored
I is probably a bug if the deltachain computation think there was a cache hit at nullrev. Use None instead, this will never trigger a cache hit.
-
Benoit Boissinot authored
Rename some variables, making the name more obvious (in particular "cache" was actually two different variable. Move code around, moving the index preloading before the deltachain computation, without that index preloading was useless (everything was read in deltachain).
-
David Soria Parra authored
-
Patrick Mezard authored
-
Patrick Mezard authored
The fallback was introduced by 3b4f05ff3130 at the same time than nlinks(). Apparently it only handles the case where target path does not exist. Just raise IOError directly.
-
Patrick Mezard authored
win32.nlinks() was often returning 1 instead of the correct hardlinks count when reading from network drives. This made commit or push to a repository on a network share to fail breaking the hardlinks in the datastore, possibly causing integrity errors in repositories linked locally on the remote side. Here is what the MSDN says about GetFileInformationByHandle(): Depending on the underlying network features of the operating system and the type of server connected to, the GetFileInformationByHandle function may fail, return partial information, or full information for the given file. In practice, we never got the correct hardlinks count when reading from and to many combinations of Window XP, 2003, Vista and 7, via network drives or RDP shares. It always returned 1 instead. The only setup returning an accurate links count was a samba on Debian. To avoid this, Mercurial now breaks the hardlinks unconditionally when writing to a network drive.
-
Matt Mackall authored
-
- Aug 18, 2010
-
-
Steve Losh authored
This patch changes the functionality of shell aliases to add more powerful options for working with shell alias arguments. First: the alias name + arguments to a shell alias are set as an HG_ARGS environment variable, delimited by spaces. This matches the behavior of hooks. Second: any occurrences of "$@" (without quotes) are replaced with the arguments, separated by spaces. This happens *before* the alias gets to the shell. Third: any positive numeric variables ("$1", "$2", etc) are replaced with the appropriate argument, indexed from 1. "$0" is replaced with the name of the alias. Any "extra" numeric variables are replaced with an empty string. This happens *before* the alias gets to the shell. These changes allow for more flexible shell aliases: [alias] echo = !echo $@ count = !hg log -r "$@" --template='.' | wc -c | sed -e 's/ //g' qqueuemv = !mv "`hg root`/.hg/patches-$1" "`hg root`/.hg/patches-$2" In action: $ hg echo foo foo $ hg count 'branch(default)' 901 $ hg count 'branch(stable) and keyword(fixes)' 102 $ hg qqueuemv myfeature somefeature
-
Steve Losh authored
util.interpolate can be used to replace multiple items in a string all at once (and optionally apply a function to the replacement), without worrying about recursing: >>> import util >>> s = '$foo, $spam' >>> util.interpolate(r'\$', { 'foo': 'bar', 'spam': 'eggs' }, s) 'bar, eggs' >>> util.interpolate(r'\$', { 'foo': 'spam', 'spam': 'foo' }, s) 'spam, foo' >>> util.interpolate(r'\$', { 'foo': 'spam', 'spam': 'foo' }, s, lambda s: s.upper()) 'SPAM, FOO' The patch also changes filemerge.py to use this new function.
-
Brodie Rao authored
The latter may not return useful results in certain OS X environments.
-
Brodie Rao authored
-