unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jens Schmidt via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63627@debbugs.gnu.org
Subject: bug#63627: Improve plstore.el and fix various issues of it
Date: Thu, 7 Sep 2023 21:27:13 +0200	[thread overview]
Message-ID: <82b540c7-403b-3904-a16d-bda3c084f78a@vodafonemail.de> (raw)
In-Reply-To: <83r0naz6s1.fsf@gnu.org>

On 2023-09-07  11:12, Eli Zaretskii wrote:
>> Date: Mon, 4 Sep 2023 00:22:52 +0200
>> Cc: 63627@debbugs.gnu.org
>> From: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
> 
> If the changeset is now ready to be installed on master, please tell.

I consider it ready to be installed on master, yes, and self-contained,
but:

>> The rest of the tests should be more or less standard.  Except
>> probably for the fact that there is still much infrastructure and few
>> actual tests, but I plan to change that.
> 
> This seems to imply that you are still working on this changeset?

I plan for plstore.el:

1. Two bug fixes on emacs-29 that I would like to add tests for on
   master once the bug fixes have made their way to master.

2. More tests and new features on emacs-master.

All of the above will still take some time to implement due to time
constraints.

For all of the above it would be convenient to have the infrastructure
of the plstore tests committed on master or at least agreed upon so
that I can build on that.

Not sure how you prefer to get such long-running projects presented -
as a series of minor (but self-contained!) patches over time or at
once as one big set of patches.

Thanks.





  reply	other threads:[~2023-09-07 19:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-21 15:45 bug#63627: Improve plstore.el and fix various issues of it Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-22 20:11 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-31 12:54   ` Eli Zaretskii
2023-06-16 19:43     ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-30 19:28     ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-31  4:46       ` Eli Zaretskii
2023-08-31 10:21         ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-02  7:41           ` Eli Zaretskii
2023-09-03 22:22             ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-07  9:12               ` Eli Zaretskii
2023-09-07 19:27                 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-08  5:40                   ` Eli Zaretskii
2023-09-08  9:16                     ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08 11:34                       ` Eli Zaretskii
2023-09-08 21:24                         ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-14 21:24                         ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-16 10:13                           ` Eli Zaretskii
2023-09-16 10:35                             ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-16 11:07                               ` Eli Zaretskii

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=82b540c7-403b-3904-a16d-bda3c084f78a@vodafonemail.de \
    --to=bug-gnu-emacs@gnu.org \
    --cc=63627@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jschmidt4gnu@vodafonemail.de \
    /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).