From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Philip Kaludercic <philipk@posteo.net>
Cc: relekarpayas@gmail.com, johnw@gnu.org, monnier@iro.umontreal.ca,
emacs-devel@gnu.org
Subject: Re: Adding use-package to core
Date: Wed, 16 Nov 2022 16:33:03 -0800 [thread overview]
Message-ID: <CADwFkmmqEqqDk2ErjzvDWOuQPNp2mFChHjkpFZMR=55ruDb_=g@mail.gmail.com> (raw)
In-Reply-To: <83h6yyg0l5.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> What is the alternative? If you copy all the issues to debbugs, you
> have the same problem. And it is impractical to expect us to solve
> all the issues before importing use-package, and also impractical to
> update the issues in GitHub after the import.
>
> So I don't think there's any better solution than gradually work on
> the issues via debbugs. That is, for every issue we want to solve,
> file a debbugs bug report, and then work there.
We could archive it after some grace period, say 3, 6, or N months.
At the beginning of that period, we could add a comment to all open
issues and pull requests, saying where to report the issue. At the end,
we could do it again. Then we archive.
next prev parent reply other threads:[~2022-11-17 0:33 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 15:29 Adding use-package to core Payas Relekar
2022-11-16 16:04 ` Philip Kaludercic
2022-11-16 16:51 ` Eli Zaretskii
2022-11-16 17:01 ` Philip Kaludercic
2022-11-16 19:29 ` Eli Zaretskii
2022-11-17 0:33 ` Stefan Kangas [this message]
2022-11-17 6:40 ` Eli Zaretskii
2022-11-17 7:17 ` Stefan Kangas
2022-11-17 7:24 ` Payas Relekar
2022-11-17 16:18 ` John Wiegley
2022-11-17 7:33 ` Eli Zaretskii
2022-11-17 7:58 ` Stefan Kangas
-- strict thread matches above, loose matches on Subject: below --
2022-11-18 0:32 Payas Relekar
2022-11-16 14:18 Payas Relekar
2022-11-16 14:52 ` Eli Zaretskii
2022-11-16 19:35 ` John Wiegley
2022-11-16 8:28 Payas Relekar
2022-11-16 9:30 ` Stefan Kangas
2022-11-16 13:35 ` Eli Zaretskii
2022-11-13 16:11 xenodasein--- via Emacs development discussions.
2022-11-13 16:48 ` Eli Zaretskii
2022-11-13 17:53 ` John Wiegley
2022-11-13 18:13 ` Eli Zaretskii
2022-11-13 18:45 ` John Wiegley
2022-11-13 18:05 ` Stefan Kangas
[not found] ` <838rkels13.fsf@gnu.org-NGltIw7----9>
2022-11-13 18:12 ` xenodasein--- via Emacs development discussions.
2022-11-13 18:22 ` Stefan Kangas
2022-11-13 18:31 ` Eli Zaretskii
2022-11-13 19:19 ` xenodasein--- via Emacs development discussions.
2022-11-13 20:08 ` Eli Zaretskii
2022-11-13 18:46 ` John Wiegley
2022-11-13 19:02 ` xenodasein--- via Emacs development discussions.
2022-11-13 19:48 ` John Wiegley
2022-11-13 20:04 ` Eli Zaretskii
2022-11-14 10:32 ` xenodasein--- via Emacs development discussions.
2022-11-14 13:30 ` Eli Zaretskii
2022-11-14 0:27 ` Po Lu
2022-11-14 10:12 ` xenodasein--- via Emacs development discussions.
2022-11-14 10:47 ` Po Lu
2022-11-14 11:52 ` xenodasein--- via Emacs development discussions.
2022-11-14 12:19 ` Po Lu
2022-11-15 15:39 ` Michael Albinus
2022-11-14 13:54 ` Eli Zaretskii
2022-11-14 14:47 ` xenodasein--- via Emacs development discussions.
2022-11-14 17:39 ` Eli Zaretskii
2022-11-15 15:38 ` xenodasein--- via Emacs development discussions.
2022-11-15 19:22 ` Eli Zaretskii
2022-11-18 19:29 ` Sean Whitton
2022-11-18 19:33 ` Philip Kaludercic
2022-11-18 19:42 ` Eli Zaretskii
2022-11-18 20:43 ` Philip Kaludercic
2022-11-19 7:12 ` Eli Zaretskii
2022-11-19 7:33 ` Philip Kaludercic
2022-11-19 8:04 ` Eli Zaretskii
2022-11-19 10:09 ` Philip Kaludercic
2022-11-19 10:31 ` Eli Zaretskii
2022-11-19 11:02 ` Philip Kaludercic
2022-11-19 11:15 ` Stefan Kangas
2022-11-19 11:58 ` Eli Zaretskii
2022-11-19 12:15 ` Philip Kaludercic
2022-11-19 15:28 ` Stefan Monnier
2022-11-19 15:36 ` Philip Kaludercic
2022-11-19 15:46 ` Eli Zaretskii
2022-11-19 15:26 ` Stefan Monnier
2022-11-13 11:55 Payas Relekar
2022-11-13 17:31 ` xenodasein--- via Emacs development discussions.
2022-11-13 17:40 ` Philip Kaludercic
2022-11-13 18:05 ` Stefan Kangas
2022-11-13 18:42 ` xenodasein--- via Emacs development discussions.
2022-11-13 18:24 ` John Wiegley
2022-11-13 7:14 Payas Relekar
2022-10-25 12:06 [ELPA] New package: use-package Payas Relekar
[not found] ` <877d0kbkfm.fsf@gmail.com>
[not found] ` <jwv8rl0nmb1.fsf-monnier+emacs@gnu.org>
[not found] ` <875yg4144y.fsf@gmail.com>
[not found] ` <jwvczablieq.fsf-monnier+emacs@gnu.org>
[not found] ` <87h6zmj451.fsf@gmail.com>
[not found] ` <5EE58F68-8B9E-4DE6-BA20-3A88FFDA6528@posteo.net>
[not found] ` <jwvh6zmit8b.fsf-monnier+emacs@gnu.org>
[not found] ` <871qqkjwjj.fsf@gmail.com>
[not found] ` <jwvr0ykw2ac.fsf-monnier+emacs@gnu.org>
2022-11-03 16:42 ` Payas Relekar
2022-11-03 16:57 ` Philip Kaludercic
2022-11-03 16:59 ` Payas Relekar
2022-11-03 17:15 ` Philip Kaludercic
2022-11-04 18:24 ` John Wiegley
2022-11-04 22:03 ` Philip Kaludercic
2022-11-05 8:06 ` Payas Relekar
2022-11-05 8:33 ` Philip Kaludercic
2022-11-05 8:45 ` Payas Relekar
2022-11-05 9:37 ` Philip Kaludercic
2022-11-05 10:13 ` Payas Relekar
2022-11-12 5:42 ` Adding use-package to core Stefan Kangas
2022-11-12 7:25 ` Philip Kaludercic
2022-11-12 10:17 ` Stefan Kangas
2022-11-12 14:04 ` Philip Kaludercic
2022-11-12 15:38 ` Stefan Kangas
2022-11-12 15:46 ` Philip Kaludercic
2022-11-12 15:53 ` Payas Relekar
2022-11-12 16:33 ` Philip Kaludercic
2022-11-13 4:43 ` John Wiegley
2022-11-13 5:25 ` Stefan Kangas
2022-11-13 7:07 ` Philip Kaludercic
2022-11-13 7:31 ` Eli Zaretskii
2022-11-13 14:09 ` Stefan Kangas
2022-11-13 15:22 ` Philip Kaludercic
2022-11-13 15:42 ` Stefan Kangas
2022-11-15 17:25 ` Philip Kaludercic
2022-11-16 4:17 ` Stefan Kangas
2022-11-16 7:59 ` Philip Kaludercic
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='CADwFkmmqEqqDk2ErjzvDWOuQPNp2mFChHjkpFZMR=55ruDb_=g@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=johnw@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
--cc=relekarpayas@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).