all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: Po Lu <luangruo@yahoo.com>, 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 14:57:23 +0300	[thread overview]
Message-ID: <afb8bd73-8a25-4270-27fd-ad346ccc9fda@gutov.dev> (raw)
In-Reply-To: <87zg4v69v7.fsf@yahoo.com>

On 19/06/2023 13:10, Po Lu wrote:
> At my organization, which uses SVN, each new revision
> is required to change only one file, and updates to ChangeLog are
> performed separately after all edits are checked in and the
> corresponding files are unlocked.  This is also the same policy that was
> used by Emacs development in the CVS days, I think.

Sounds like your organization uses a fairly antiquated workflow.

Luckily, we're a few steps ahead now in Emacs development.



  reply	other threads:[~2023-06-19 11:57 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
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 [this message]
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=afb8bd73-8a25-4270-27fd-ad346ccc9fda@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=hi-angel@yandex.ru \
    --cc=luangruo@yahoo.com \
    /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.