unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jens Schmidt <jschmidt4gnu@vodafonemail.de>,
	Andrew G Cohen <cohen@andy.bu.edu>
Cc: 63497@debbugs.gnu.org
Subject: bug#63497: [PATCH] Remove obsolete information on archiving mail from Gnus manual
Date: Thu, 18 May 2023 14:10:37 +0300	[thread overview]
Message-ID: <835y8px5ci.fsf@gnu.org> (raw)
In-Reply-To: <c04edb61-5823-b44e-9307-73757355eab7@vodafonemail.de> (bug-gnu-emacs@gnu.org)

> Date: Sat, 13 May 2023 21:28:37 +0200
> From:  Jens Schmidt via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> my first test patch to practice things, pls comment if its format is not 
> what you expect.  I hope Thunderbird does not mess up the format.  FSF 
> copyright assignment is in process, but probably not yet completed.

It's not.

> Regardless of this being a test patch, it fixes a real but minor doc 
> issue in the Gnus manual:  In 2012 Lars committed a change that removed 
> the previous "external marks" feature  from various backends 
> (89b163db286d79b43fb5c9927fc622bbf7d2ef1a).
> 
> The Gnus manual still references these external marks in section 
> "Archiving Mails", I guess that reference just got overlooked.  But 
> without external marks, archiving mails in Gnus is rather difficult (to 
> my knowledge), at least for the nnml backend.  So I decided to rather 
> remove that section entirely.

Andrew, should these parts be removed, indeed?

> * doc/misc/gnus.texi: Remove obsolete information on archiving mail from 
> Gnus manual

Please mention the names of the nodes in which you make the changes,
as if they were functions.  (Using the Emacs commands for generating
ChangeLog-style entries would automatically include those node names
for you, so it is recommended to use those commands.)

Also, once you know the bug number (which usually happens when you
submit the second version of the patch and all the subsequent
versions), please mention the bug number in the commit log message.
You can see examples of that if you type "git log" in the Emacs
repository.

Thanks.





  reply	other threads:[~2023-05-18 11:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-13 19:28 bug#63497: [PATCH] Remove obsolete information on archiving mail from Gnus manual Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-18 11:10 ` Eli Zaretskii [this message]
2023-05-19  0:39   ` Andrew Cohen
2023-05-19  6:08     ` Eli Zaretskii
2023-05-20 21:51 ` bug#63497: [PATCH] Remove obsolete information on archiving mail Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-21  6:26   ` 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=835y8px5ci.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=63497@debbugs.gnu.org \
    --cc=cohen@andy.bu.edu \
    --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).