All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: What's cooking in git.git (Apr 2018, #01; Mon, 9)
Date: Wed, 11 Apr 2018 22:51:38 +0200	[thread overview]
Message-ID: <87in8xbh5x.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <86d0z560m8.fsf@gmail.com>


On Wed, Apr 11 2018, Jakub Narebski wrote:

> 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?

I've just submitted a v4 which should address the issue raised in v3,
which was that we don't want to delete the files, but instead have a
boilerplate *.el file that errors out, thus helping e.g. users of git-el
in Debian to migrate.

See
https://public-inbox.org/git/20180411204206.28498-1-avarab@gmail.com/

      reply	other threads:[~2018-04-11 20:51 UTC|newest]

Thread overview: 23+ 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: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
2018-04-11 20:51   ` Ævar Arnfjörð Bjarmason [this message]

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=87in8xbh5x.fsf@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    --cc=jrnieder@gmail.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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.