- Apr 16, 2010
-
-
Dévai Tamás authored
The DESTDIR variable used to tell 'make install' an alternate system root to install the software to. Since setup.py supports the same via its --root parameter, it's easy to make life easier for many packagers.
-
- Apr 12, 2010
-
-
Steve Losh authored
Fixes issue2078 and adds tests to cover various 'hg log -b' uses. This change adds a localrepo.lookupbranch(key, remote=None) function. This will look up the branch of the revision with the given key. The algorithm works like this: * If a remote repo is given and KEY is the name of a branch in that repo, return KEY. * If no remote repo is given and KEY is the name of a branch in the local repo object, return KEY. * Otherwise look up the revision with the identifier KEY in the local repo and return its branch. This change also makes 'hg log -b' use this new functionality and adds a few tests for it.
-
- Apr 19, 2010
-
-
Matt Mackall authored
-
Matt Mackall authored
-
- Apr 18, 2010
-
-
Steve Losh authored
Switching to --branch makes log consistent with push/pull and make more sense given the actual behavior of the option (you can specify -b multiple times to include multiple branches). This change also adds some tests for 'hg log -b'.
-
- Apr 17, 2010
-
-
Isaac Jurado authored
The fix for issue1611 left one last use of "repo" instead of "self" that has resulted in more memory leaks from push/pull operations.
-
- Apr 07, 2010
-
-
Elifarley Callado Coelho Cruz authored
pre-commit time too. This is useful because now it's possible to avoid violating ACL permissions much sooner, at commit time, instead of waiting for a PUSH to check if there were any invalid commits.
-
- Apr 19, 2010
-
-
Benoit Boissinot authored
-
Benoit Boissinot authored
I checked the tests, they were bogus in the first place
-
Benoit Boissinot authored
-
Benoit Boissinot authored
_fileid can be anything the lookup accepts (hex(node), node, rev, etc.), we should use something stable for comparisons (like _filenode).
-
Martin Geisler authored
-
- Apr 18, 2010
-
-
Martin Geisler authored
-
Martin Geisler authored
-
Martin Geisler authored
We should strive to avoid slang in our messages to the users.
-
Martin Geisler authored
-
Martin Geisler authored
This greatly improves the output of 'hg help env'.
-
- Apr 16, 2010
-
-
Benoit Boissinot authored
-
Martin Geisler authored
-
- Apr 14, 2010
-
-
Faheem Mitha authored
-
- Apr 15, 2010
-
-
Dan Villiom Podlaski Christiansen authored
Restore the behaviour introduced in e37e9904bf10, which was accidentally removed when labelling was introduced in 717c35d55fb3.
-
- Apr 16, 2010
-
-
Christian Ebert authored
-
Adrian Buehlmann authored
- using FileSource attribute - removed unneeded "DiskId='1'" - all guids are now in guids.wxi
-
- Apr 15, 2010
-
-
Benoit Boissinot authored
-
Benoit Boissinot authored
-
Benoit Boissinot authored
-
Sune Foldager authored
-
Sune Foldager authored
For servers with branchmap support, the algorithm now works as follows: 1. A list of branches in outgoing changesets is created. 2. Using the remote branchmap, a check for new branches is performed. 3. A map (from branch to head list) of locally known remote heads before the push is created, and one which, after step 4, will contain the locally known remote heads after the push. 4. The post-push head map is updated with the outgoing changesets, using the branch cache update mechanism. 5. A check for new heads is performed, by comparing the length of the head list before and after push, for each branch. If there are new heads, an error depending on whether or not there are incoming changes on the branch, is returned. 6. If the push is allowed, a warning is written if there are incoming changes on any branches involved in the push. For old servers, an algorithm similar to step 4-6 above is used to check for new topological heads only. Two bugs are also fixed: 1. Sometimes you would be allowed to push new branch heads without --force. A test for this case was added. 2. You would get the "note: unsynced remote changes!" warning if there were any incoming changesets, even if they were on unrelated branches.
-
Benoit Boissinot authored
-
Benoit Boissinot authored
-
Benoit Boissinot authored
-
Benoit Boissinot authored
This bug happens if the filesystem doesn't support exec-bit, during merges, for example in 24ed7a541f23 on the hg repo. If f is not in p1, but is in p2 and has the x-bit in p2, since the dirstate is based on p1, and the FS doesn't support the exec-bit, the dirstate can't "guess" the right bit. We instead fix it in workingcontext.flags()/manifest.
-
Sune Foldager authored
-
Benoit Boissinot authored
-
Benoit Boissinot authored
-
Benoit Boissinot authored
-
Benoit Boissinot authored
-
Benoit Boissinot authored
-
- Apr 14, 2010
-
-
Greg Ward authored
Previously, it only returned revisions that were in the revlog when it was originally opened; revisions added since then were invisible. This broke revlog._partialmatch() and therefore repo.lookup(). (Credit to Benoit Boissinot for simplifying my original test script and for the actual fix.)
-
- Apr 13, 2010
-
-
Greg Ward authored
This lets us change the threshold at which a *.d file will be split out, which should make it much easier to construct test cases that probe revlogs with a separate data file. (issue2137)
-