9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Nick Owens <mischief@offblast.org>
To: 9front@9front.org
Subject: Re: [9front] bug: hg pull fails on a bitbucket repo
Date: Wed, 28 Nov 2018 13:05:38 -0800	[thread overview]
Message-ID: <CAH_zEu6XzenKUp1wQZdiEqFHc+nd979bwL5kUr5yexKDnDjZNg@mail.gmail.com> (raw)
In-Reply-To: <F73586D94C686AABEDEB20502F566900@felloff.net>

executing diffstat on linux against plan9front's copy and mercurial 3.4.1:

 114 files changed, 34938 insertions(+), 12458 deletions(-)

it is nice that mercurial 3.4.1 already works, but it would indeed be
quite some work to replace the system hg with it.

i suppose for now i can simply encourage people to install mercurial
3.4.1 and use it instead of the system hg.
On Wed, Nov 28, 2018 at 12:41 PM <cinap_lenrek@felloff.net> wrote:
>
> noted.
>
> on very low priority for me as i dont have much time and like
> working on plan9 problems rather than python ones.
>
> this would mostly consist of doing tons of testing to see
> if there are any operational issues with the new python code.
> not just cloning bitbucket repos but actually do commits, merge,
> remove, add, diff ect... also wonder if our repo format is
> still fully supported. as people will not manually nuke ther
> /dist/.hg.
>
> see if hg serve still works...
>
> maybe add support for new repo formats to hgfs...
>
> also, how big are the differences? have you diffed the python
> code and can say how big the changes in mercurial are?
>
> --
> cinap


  reply	other threads:[~2018-11-28 21:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-28 20:40 cinap_lenrek
2018-11-28 21:05 ` Nick Owens [this message]
2018-11-28 21:40   ` hiro
2018-11-28 21:42     ` hiro
  -- strict thread matches above, loose matches on Subject: below --
2018-11-28 20:25 Nick Owens
2018-11-28 21:45 ` [9front] " hiro
2018-11-28 23:36   ` Nick Owens
2018-11-28 23:44     ` hiro
2018-11-29  0:42       ` Nick Owens
2018-11-29  1:02         ` hiro
2018-11-29  5:35           ` Kurt H Maier
2018-11-29  9:49             ` hiro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAH_zEu6XzenKUp1wQZdiEqFHc+nd979bwL5kUr5yexKDnDjZNg@mail.gmail.com \
    --to=mischief@offblast.org \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).