Log message:
Updated py-hg-git to 0.8.5.
init: mark Mercurial 3.7 as supported and prepare for 0.8.5
test-help: fix for Mercurial 3.7
test-renames.t: don't use "seq"
push: better formatting of messages from the server
git_handler: use util method for writing bookmarks
util: add method for writing bookmarks
util: regularize mercurial imports
ignore: add .testtimes to ignored files
version: bump up to 0.8.4
all-version-tests: test Mercurial 3.6.3
git_handler: work around dulwich using unicode for ref names Dulwich treats ref \
names internally as unicode strings (probably because of Python 3?), which means \
that at some points it tries to do os.path.join between the repo path and the \
unicode of the ref name, which fails miserably if we construct the repo with a \
str and not a unicode. Kludge around this problem. Fixes issue 172. This is a \
roll-forward of a593069575bb, which should be valid now that thâ¦
hgrepo: ensure all git-origin tags are bytes If we don't do this we might end up \
with unicodes being written using ui, which then breaks in popbuffer in \
test-encoding.t. This appears to be an academic concern until we start passing \
unicode paths to git repos, which we need to do in order to resolve some other \
problems. Yay.
all-version-tests: wrap to 80 columns and test 3.{5,6}.2
Makefile: respect HGTESTFLAGS environment variable
test-push.t: clean up compat cruft
testutil: clean up compat cruft
test-subrepos.t: clean up compat cruft
gitdirstate: fix up compat comment pathutil isn't in 2.8.
gitrepo: clean up compat cruft
merge
overlay: regularize mercurial imports
gitdirstate: regularize mercurial imports
ssh: regularize mercurial imports
hgrepo: regularize mercurial imports
hg2git: regularize mercurial imports
init: regularize mercurial imports
git_handler: regularize mercurial imports
bookmarks: use bookmarks.recordchange instead of bookmarks.write if available \
bookmarks.write is deprecated and it was showing warning messages in \
test-hg-branch.t with the latest test runner from core mercurial. Tested with \
both hg 2.8 and hg tip.
init: handle AttributeError in addition to ImportError If a module doesn't \
exist, it yields an ImportError, if an attribtue doesn't exist on a module, it \
yields an AttributeError
ssh: fix breakage again with dulwich update dulwich 0.12.x changed the way they \
pass parameters around, so we reformat that to what hg-git expects. This is just \
plain ridiculous.
push: print messages from the server Some servers, for example, Bitbucket, \
output helpful messages. This patch reports the output, if any exist, to the \
user.
init: only activate git ignore logic in reposetup This will massively speed up \
'hg status' on repos that are not git based. On my macports repo, status went \
from Before: 0m0.591s After: 0m0.297s
Backed out changeset a593069575bb This was causing test-encoding.t to fail.
git_handler: work around dulwich using unicode for ref names Dulwich treats ref \
names internally as unicode strings (probably because of Python 3?), which means \
that at some points it tries to do os.path.join between the repo path and the \
unicode of the ref name, which fails miserably if we construct the repo with a \
str and not a unicode. Kludge around this problem. Fixes issue 172.
readme: document the specific behaviors of hg author translation Particularly \
the odd ext:(%xx) feature.
manifest: include test and test data Closes issue #154.
determine_wants: deal with refs being None Not clear how this is happening, but \
this should fix it. Resolves issue #166.
|
Log message:
Import py27-hg-git-0.8.1 as devel/py-hg-git.
This is the Hg-Git plugin for Mercurial, adding the ability to push
and pull to/from a Git server repository from Hg. This means you can
collaborate on Git based projects from Hg, or use a Git server as a
collaboration point for a team with developers using both Git and Hg.
The Hg-Git plugin can convert commits/changesets losslessly from one
system to another, so you can push via an Hg repository and another Hg
client can pull it and their changeset node ids will be identical -
Mercurial data does not get lost in translation. It is intended that
Hg users may wish to use this to collaborate even if no Git users are
involved in the project, and it may even provide some advantages if
you're using Bookmarks.
|