From: Emanuel Berg <incal@dataswamp.org>
To: emacs-devel@gnu.org
Subject: Re: wrap-search 3.3.5
Date: Fri, 02 Sep 2022 23:10:43 +0200 [thread overview]
Message-ID: <8735d9zdm4.fsf@dataswamp.org> (raw)
In-Reply-To: 2f302d1c39989cae747e@heytings.org
Gregory Heytings wrote:
>> Alternatively, one might stop trying to automate commits
>> and actually write useful commit messages when and if
>> a functionally complete set of changes is finished.
>
> Emanuel wanted something completely automated that would not
> change his existing workflow. Useful commit messages are
> better of course, but automated commit messages aren't
> a catastrophe.
Well, I don't really care how well-documented the process of
"development" - or programming as I like to call it - is.
Maybe at some point the complexity of software gets so big
such documentation is actually useful for further work on it,
i.e. the software, but not with 106 lines of Elisp with
3 defuns, for sure.
Not saying there's anything wrong with those 106 lines ... on
the contrary.
Anyway I'm happy to sign whatever agreement you are speaking
of and close the book on this?
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-09-02 21:10 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 18:28 wrap-search 3.3.5 Emanuel Berg
2022-08-25 18:34 ` Philip Kaludercic
2022-08-25 18:50 ` Emanuel Berg
2022-08-25 19:05 ` Philip Kaludercic
2022-08-25 19:15 ` Emanuel Berg
2022-08-25 20:48 ` Philip Kaludercic
2022-08-26 19:46 ` Emanuel Berg
2022-08-26 23:46 ` Philip Kaludercic
2022-08-27 0:06 ` Emanuel Berg
2022-08-27 8:24 ` Philip Kaludercic
2022-08-28 0:13 ` Emanuel Berg
2022-08-28 8:07 ` Philip Kaludercic
2022-08-28 8:30 ` Andreas Schwab
2022-08-28 8:43 ` Emanuel Berg
2022-08-28 9:00 ` Philip Kaludercic
2022-08-28 21:02 ` Emanuel Berg
2022-08-28 21:24 ` Gregory Heytings
2022-08-28 21:31 ` Emanuel Berg
2022-08-28 21:33 ` Emanuel Berg
2022-08-29 6:28 ` Yuri Khan
2022-08-31 2:06 ` Emanuel Berg
2022-08-31 9:04 ` Philip Kaludercic
2022-08-31 9:29 ` Emanuel Berg
2022-08-31 10:42 ` Gregory Heytings
2022-08-31 11:04 ` Emanuel Berg
2022-08-31 12:24 ` Gregory Heytings
2022-08-31 15:08 ` Emanuel Berg
2022-08-31 15:18 ` Gregory Heytings
2022-08-31 21:31 ` Emanuel Berg
2022-08-31 21:45 ` [External] : " Drew Adams
2022-09-01 4:27 ` tomas
2022-08-31 21:55 ` Emanuel Berg
2022-08-31 22:08 ` Gregory Heytings
2022-09-01 0:46 ` Emanuel Berg
2022-09-01 11:21 ` Gregory Heytings
2022-09-01 17:02 ` Emanuel Berg
2022-09-01 18:20 ` Gregory Heytings
2022-09-01 19:17 ` Emanuel Berg
2022-09-01 20:01 ` Gregory Heytings
2022-09-01 20:52 ` Emanuel Berg
2022-09-01 21:59 ` Gregory Heytings
2022-09-01 22:20 ` Emanuel Berg
2022-09-02 8:55 ` Yuri Khan
2022-09-02 9:03 ` Gregory Heytings
2022-09-02 21:10 ` Emanuel Berg [this message]
2022-08-31 14:54 ` Philip Kaludercic
2022-08-31 15:09 ` Emanuel Berg
2022-08-25 21:46 ` [External] : " Drew Adams
2022-08-25 20:26 ` Stefan Monnier
2022-08-25 22:08 ` Emanuel Berg
2022-08-25 22:23 ` Emanuel Berg
2022-08-26 1:10 ` Stefan Monnier
2022-08-26 2:17 ` Emanuel Berg
2022-08-25 22:47 ` Emanuel Berg
2022-08-25 22:19 ` Emanuel Berg
2022-08-26 10:17 ` Emanuel Berg
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=8735d9zdm4.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=emacs-devel@gnu.org \
/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).