Felipe Contreras <felipe.contreras@xxxxxxxxx> writes: > Here is the next round of patches for remote-hg, some which have been > contributed through github. Thanks. > Fortunately it seems to be working for the most part, but there are some > considerable issues while pushing branches and tags. Do you have a plan in mind what to do about "some considerable issues"? I could push these out to 'master' and let the interested parties sort it out---having early access to the code everybody bases his effort on would help. I could queue these on 'pu' and do the same, and wait until you say "now it is ready, let's go to 'next'" (and same for 'master'). Or are they meant as "There are issues, but here is a snapshot of what I have at this moment. Hopefully others can help me update it by trying it out and discussing, which may lead me to post a reroll for application"? I'll queue them on 'pu' in the meantime. > > Dusty Phillips (1): > remote-hg: add missing config variable in doc > > Felipe Contreras (11): > remote-hg: trivial cleanups > remote-hg: properly report errors on bookmark pushes > remote-hg: make sure fake bookmarks are updated > remote-hg: trivial test cleanups > remote-hg: redirect buggy mercurial output > remote-hg: split bookmark handling > remote-hg: refactor export > remote-hg: update remote bookmarks > remote-hg: force remote push > remote-hg: don't update bookmarks unnecessarily > remote-hg: update tags globally > > Peter van Zetten (1): > remote-hg: fix for files with spaces > > contrib/remote-helpers/git-remote-hg | 73 ++++++++++++++++++++++++-------- > contrib/remote-helpers/test-hg-bidi.sh | 6 +-- > contrib/remote-helpers/test-hg-hg-git.sh | 4 +- > 3 files changed, 61 insertions(+), 22 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html