From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2018, #01; Mon, 9)
Date: Wed, 11 Apr 2018 20:47:59 +0200 [thread overview]
Message-ID: <86d0z560m8.fsf@gmail.com> (raw)
In-Reply-To: <xmqqd0z865pk.fsf@gitster-ct.c.googlers.com> (Junio C. Hamano's message of "Mon, 09 Apr 2018 19:21:11 +0900")
Junio C Hamano <gitster@pobox.com> writes:
> * ab/nuke-emacs-contrib (2018-03-13) 1 commit
> (merged to 'next' on 2018-03-15 at 13eb4e2d8b)
> + git{,-blame}.el: remove old bitrotting Emacs code
>
> The scripts in contrib/emacs/ have outlived their usefulness and
> have been removed.
>
> Will kick back to 'pu'.
>
> There were some noises about better migration strategy that lets
> git.el to nudge users to magit or something when used. Is it
> something we want to pursue further?
Maybe simply delete all files, leaving only README pointing to Magit?
Best,
--
Jakub Narębski
next prev parent reply other threads:[~2018-04-11 20:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 10:21 What's cooking in git.git (Apr 2018, #01; Mon, 9) Junio C Hamano
2018-04-09 13:37 ` Derrick Stolee
2018-04-09 16:49 ` Ramsay Jones
2018-04-09 22:08 ` Junio C Hamano
2018-04-10 12:57 ` Derrick Stolee
2018-04-10 19:12 ` Stefan Beller
2018-04-10 19:21 ` Ramsay Jones
2018-04-10 19:21 ` Ramsay Jones
2018-04-10 19:35 ` Derrick Stolee
2018-04-10 20:22 ` Ramsay Jones
2018-04-10 20:37 ` Ramsay Jones
2018-04-10 21:46 ` Junio C Hamano
2018-04-09 15:31 ` Duy Nguyen
2018-04-09 17:23 ` Stefan Beller
2018-04-09 20:14 ` Johannes Schindelin
2018-04-09 21:32 ` Johannes Schindelin
2018-04-10 12:25 ` Johannes Schindelin
2018-04-10 21:02 ` git-gui branches, was " Johannes Schindelin
2018-04-10 21:38 ` Junio C Hamano
2018-04-10 21:54 ` Stefan Beller
2018-04-10 22:41 ` Johannes Schindelin
2018-04-11 10:13 ` Phillip Wood
2018-04-11 18:47 ` Jakub Narebski [this message]
2018-04-11 20:51 ` Ævar Arnfjörð Bjarmason
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86d0z560m8.fsf@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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://80x24.org/mirrors/git.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).