From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] bug: hg pull fails on a bitbucket repo
Date: Wed, 28 Nov 2018 22:40:37 +0100 [thread overview]
Message-ID: <CAFSF3XN_xPBmg03d_AvWwyUTz88LdVMfv84O8+OeRF=khV+Rxw@mail.gmail.com> (raw)
In-Reply-To: <CAH_zEu6XzenKUp1wQZdiEqFHc+nd979bwL5kUr5yexKDnDjZNg@mail.gmail.com>
why didn't you do diff between the mercurial 9front is BASED on and
mercurial 3.4.1 ?!
we already know there were tons of changes in 9front's copy. this is
thus worthless information.
next prev parent reply other threads:[~2018-11-28 21:40 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
2018-11-28 21:40 ` hiro [this message]
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='CAFSF3XN_xPBmg03d_AvWwyUTz88LdVMfv84O8+OeRF=khV+Rxw@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).