From: zimoun <zimon.toutoune@gmail.com>
To: 38272@debbugs.gnu.org, Marius Bakke <mbakke@fastmail.com>,
David Wilson <david@daviwil.com>
Subject: [bug#38272] [PATCH] gnu: Add emacs-openwith.
Date: Fri, 22 Nov 2019 15:05:35 +0100 [thread overview]
Message-ID: <CAJ3okZ1Cox-uY8CceqZRsSjB1XRR_ZHB1rCPbh2-NecXtC5PvQ@mail.gmail.com> (raw)
In-Reply-To: <87tv6x6pq6.fsf@devup.no>
Hi Marius,
On Thu, 21 Nov 2019 at 19:37, Marius Bakke <mbakke@fastmail.com> wrote:
> But, I read in another message that BitBucket is shutting down Mercurial
> support in 2020, so I'm not sure what to do about it. Thoughts?
The timeline of the shutdown is here [1] so we have still some time. :-)
The best seems to first list all the packages offended via some scheme
code -- I have no idea how many packages will be impacted.
Then contact each upstream to know what is their plan, i.e., where the
new location of the source will be: git conversion and still on
BitBucket; still hg and move to elsewhere; etc.
I do not know if it is better to open only one bug report to track the
progress (maybe my preference), or to open one bug report per package.
What do you think?
All the best,
simon
[1] https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket
next prev parent reply other threads:[~2019-11-22 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 15:17 [bug#38272] [PATCH] gnu: Add emacs-openwith David Wilson
2019-11-19 20:21 ` Marius Bakke
2019-11-20 13:53 ` David Wilson
2019-11-21 18:36 ` bug#38272: " Marius Bakke
2019-11-22 14:05 ` zimoun [this message]
2019-11-24 22:28 ` [bug#38272] " Marius Bakke
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ1Cox-uY8CceqZRsSjB1XRR_ZHB1rCPbh2-NecXtC5PvQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=38272@debbugs.gnu.org \
--cc=david@daviwil.com \
--cc=mbakke@fastmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).