From: Drew Adams <drew.adams@oracle.com>
To: uzibalqa <uzibalqa@proton.me>, Po Lu <luangruo@yahoo.com>
Cc: "tomas@tuxteam.de" <tomas@tuxteam.de>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: Source code, git and cvs
Date: Fri, 21 Jul 2023 14:20:09 +0000 [thread overview]
Message-ID: <SJ0PR10MB54889AE31C00B12082C173E1F33FA@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <du7QslEK76Xx6sGLpDLkeHWd9h3_3e5XYcsqtytRswZoYDkCNiq9Byl6S8NLEAm7DkgCFQfL4y1Hse2Rg9MdSpQbJYgXNys7wOfc0pczVs0=@proton.me>
> An automated tool would be able to do it
> better than you. Otherwise the way the
> documentation is designed has to change.
(Apologies to others for tossing a stick
on the dump fire...)
A whiner/kvetcher bot would be able to
do what you're doing here as well as you.
Maybe hone your Elisp skills by writing
one, then retire the man-child griping?
Only half-kidding.
next prev parent reply other threads:[~2023-07-21 14:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 12:01 Source code, git and cvs uzibalqa
2023-07-20 13:38 ` Po Lu
2023-07-20 13:58 ` uzibalqa
2023-07-20 14:23 ` Eli Zaretskii
2023-07-20 15:09 ` uzibalqa
2023-07-20 15:34 ` Robert Pluim
2023-07-20 15:36 ` Eli Zaretskii
2023-07-20 15:47 ` uzibalqa
2023-07-20 16:35 ` Eli Zaretskii
2023-07-20 17:33 ` uzibalqa
2023-07-20 18:31 ` Eli Zaretskii
2023-07-20 19:12 ` uzibalqa
2023-07-20 20:10 ` uzibalqa
2023-07-21 5:22 ` Eli Zaretskii
2023-07-21 6:12 ` Po Lu
2023-07-21 10:43 ` uzibalqa
2023-07-21 10:59 ` uzibalqa
2023-07-21 11:18 ` uzibalqa
2023-07-21 12:30 ` Eli Zaretskii
2023-07-21 12:40 ` uzibalqa
2023-07-21 12:51 ` Eli Zaretskii
2023-07-21 4:27 ` tomas
2023-07-21 10:35 ` uzibalqa
2023-07-21 12:12 ` Po Lu
2023-07-21 12:52 ` uzibalqa
2023-07-21 14:20 ` Drew Adams [this message]
2023-07-21 15:30 ` [External] : " uzibalqa
2023-07-20 16:05 ` uzibalqa
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=SJ0PR10MB54889AE31C00B12082C173E1F33FA@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=luangruo@yahoo.com \
--cc=tomas@tuxteam.de \
--cc=uzibalqa@proton.me \
/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 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).