From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] bug: hg pull fails on a bitbucket repo
Date: Thu, 29 Nov 2018 02:02:03 +0100 [thread overview]
Message-ID: <CAFSF3XNVn7c5fOmk0fvBnvoyRmKg2_77H61hiyS0Ai3DpXuU=g@mail.gmail.com> (raw)
In-Reply-To: <CAH_zEu6BguHQ=77eTWqLB0iKvwOtw7eC7v1x6BXwyuXUjthvMg@mail.gmail.com>
let's just wait 9 more years, perhaps bitbucket will stop supporting hg then.
next prev parent reply other threads:[~2018-11-29 1:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2018-11-29 5:35 ` Kurt H Maier
2018-11-29 9:49 ` hiro
2018-11-28 20:40 cinap_lenrek
2018-11-28 21:05 ` Nick Owens
2018-11-28 21:40 ` hiro
2018-11-28 21:42 ` 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='CAFSF3XNVn7c5fOmk0fvBnvoyRmKg2_77H61hiyS0Ai3DpXuU=g@mail.gmail.com' \
--to=23hiro@gmail.com \
--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).