From: Po Lu <luangruo@yahoo.com>
To: Konstantin Kharlamov <hi-angel@yandex.ru>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: ChangeLog and commit messages
Date: Mon, 19 Jun 2023 08:48:38 +0800 [thread overview]
Message-ID: <87r0q86zvd.fsf@yahoo.com> (raw)
In-Reply-To: <327d575ab075bf4e92ca00c11548a62458fec75b.camel@yandex.ru> (Konstantin Kharlamov's message of "Sun, 18 Jun 2023 17:50:12 +0300")
Konstantin Kharlamov <hi-angel@yandex.ru> writes:
> Could you please describe some example of when this happens? As
> someone who has contributed to dozens of projects, I can say there's
> likely something odd in your workflow. If you provide details on where
> and why you have problems, I think I could give suggestions for how to
> avoid that.
When I'm working on a file, I lock (using the VCS) the files which I
need to edit. Then, as I work, I type C-x 4 a and describe the changes
being made to each function. Finally, I check in the changes made to
those locked files, and update ChangeLog.
Typically, those check-ins are made at the end of the workday, but
sometimes sooner if another developer complains that a file he wishes to
edit is locked.
next prev parent reply other threads:[~2023-06-19 0:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87a5wxb5sl.fsf.ref@yahoo.com>
2023-06-18 7:14 ` ChangeLog and commit messages Po Lu
2023-06-18 7:39 ` Eli Zaretskii
2023-06-18 7:41 ` Po Lu
2023-06-18 8:02 ` Eli Zaretskii
2023-06-18 14:50 ` Konstantin Kharlamov
2023-06-19 0:48 ` Po Lu [this message]
2023-06-19 6:25 ` Konstantin Kharlamov
2023-06-19 6:51 ` Po Lu
2023-06-19 9:07 ` Konstantin Kharlamov
2023-06-19 10:10 ` Po Lu
2023-06-19 11:57 ` Dmitry Gutov
2023-06-19 16:59 ` Eli Zaretskii
2023-06-19 17:24 ` Dmitry Gutov
2023-06-19 22:18 ` Konstantin Kharlamov
2023-06-19 16:33 ` Eli Zaretskii
2023-06-20 0:55 ` Po Lu
2023-06-23 6:50 ` Sean Whitton
2023-06-23 7:16 ` Eli Zaretskii
2023-06-18 7:44 ` Sean Whitton
2023-06-18 22:38 ` Dmitry Gutov
2023-06-19 8:52 ` Jose E. Marchesi
2023-06-18 14:03 Bruno Haible
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0q86zvd.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=hi-angel@yandex.ru \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.