unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Philip Kaludercic <philipk@posteo.net>,
	 emacs-devel@gnu.org,  Jonas Bernoulli <jonas@bernoul.li>
Subject: Re: master d506d91b1f 2/2: Make linum.el obsolete
Date: Thu, 22 Sep 2022 19:50:10 +0800	[thread overview]
Message-ID: <877d1veih9.fsf@yahoo.com> (raw)
In-Reply-To: <CADwFkm=aOMp=u6EDaLZ3RGZst3Zfc_cd_kpwVRFA6w6eXAwHNQ@mail.gmail.com> (Stefan Kangas's message of "Thu, 22 Sep 2022 04:01:21 -0700")

Stefan Kangas <stefankangas@gmail.com> writes:

>> Alternatively, how about this.  Every time an obsolete file is removed,
>> it gets moved to some other folder (i.e. obsolete-gone) that is not
>> scanned for autoloads or byte-compiled, or possibly even in a repository
>> maintained separately from the rest of Emacs.
>
> Maybe the emacsattic would be interested in keeping them around:
>
>     https://github.com/emacsattic

I'd prefer something closer to Emacs itself, and not on GitHub, which
(its other problems aside) is so slow in my country that it is
essentially nonfunctional without a proxy.

Maybe another repository under the Emacs project itself?  Or better,
lisp/obsolete-gone in the regular Emacs repository, which should allow
the VCS history to be kept.

Thanks.



  reply	other threads:[~2022-09-22 11:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <166370103866.17769.3203831255447980421@vcs2.savannah.gnu.org>
     [not found] ` <20220920191039.C61BCC00874@vcs2.savannah.gnu.org>
2022-09-21  7:50   ` master d506d91b1f 2/2: Make linum.el obsolete Philip Kaludercic
2022-09-21  8:37     ` Stefan Kangas
2022-09-21  9:45       ` Philip Kaludercic
2022-09-21 12:35         ` Stefan Kangas
2022-09-21 12:43           ` Philip Kaludercic
2022-09-21 13:58             ` Stefan Kangas
2022-09-21 16:13               ` [External] : " Drew Adams
2022-09-21 16:36                 ` Stefan Kangas
2022-09-21 18:26               ` Philip Kaludercic
2022-09-21 19:19                 ` Stefan Kangas
2022-09-22  2:59               ` Po Lu
2022-09-22 11:01                 ` Stefan Kangas
2022-09-22 11:50                   ` Po Lu [this message]
2022-09-22 13:31                     ` Stefan Monnier
2022-09-22 14:01                       ` Stefan Kangas
2022-09-22 14:15                         ` Stefan Monnier
2022-09-21 16:17             ` chad

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877d1veih9.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=jonas@bernoul.li \
    --cc=philipk@posteo.net \
    --cc=stefankangas@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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).