From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Konstantin Kharlamov Newsgroups: gmane.emacs.devel Subject: Re: ChangeLog and commit messages Date: Mon, 19 Jun 2023 09:25:35 +0300 Message-ID: References: <87a5wxb5sl.fsf.ref@yahoo.com> <87a5wxb5sl.fsf@yahoo.com> <837cs1p6bf.fsf@gnu.org> <875y7lb4k7.fsf@yahoo.com> <327d575ab075bf4e92ca00c11548a62458fec75b.camel@yandex.ru> <87r0q86zvd.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18729"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Evolution 3.48.3 Cc: Eli Zaretskii , emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jun 19 08:26:43 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qB8Lb-0004bG-QC for ged-emacs-devel@m.gmane-mx.org; Mon, 19 Jun 2023 08:26:43 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qB8Kj-00040M-5R; Mon, 19 Jun 2023 02:25:49 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qB8Kg-000403-Hm for emacs-devel@gnu.org; Mon, 19 Jun 2023 02:25:46 -0400 Original-Received: from forward500c.mail.yandex.net ([178.154.239.208]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qB8Kd-0005cY-Jg; Mon, 19 Jun 2023 02:25:45 -0400 Original-Received: from mail-nwsmtp-smtp-production-main-73.iva.yp-c.yandex.net (mail-nwsmtp-smtp-production-main-73.iva.yp-c.yandex.net [IPv6:2a02:6b8:c0c:160b:0:640:acd0:0]) by forward500c.mail.yandex.net (Yandex) with ESMTP id B31515EA72; Mon, 19 Jun 2023 09:25:37 +0300 (MSK) Original-Received: by mail-nwsmtp-smtp-production-main-73.iva.yp-c.yandex.net (smtp/Yandex) with ESMTPSA id aPZbe5dDgGk0-mw9hzhrJ; Mon, 19 Jun 2023 09:25:37 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1687155937; bh=hhJvP32j/bHBLku2ME6qtiPhsPamoaS8tFy1fGXDSBs=; h=References:Date:In-Reply-To:Cc:To:From:Subject:Message-ID; b=Wz54HdLYl1PdeW+EzRIjL2K/yqvyQSmGoxDJCewTtw58W1uLoXYqkcftxPmFrQDU9 ahsmUjZM82sbDRZ0roRlXebv2xwsyENWUFofWeBOrs93nORr8MWwp7wl22LjE2EjKH cEeI8MQwbuGfTVS7zLKJmNNcUmcUY7mc6YlFB2eU= Authentication-Results: mail-nwsmtp-smtp-production-main-73.iva.yp-c.yandex.net; dkim=pass header.i=@yandex.ru In-Reply-To: <87r0q86zvd.fsf@yahoo.com> Received-SPF: pass client-ip=178.154.239.208; envelope-from=hi-angel@yandex.ru; helo=forward500c.mail.yandex.net X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:307028 Archived-At: On Mon, 2023-06-19 at 08:48 +0800, Po Lu wrote: > Konstantin Kharlamov writes: >=20 > > 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. >=20 > When I'm working on a file, I lock (using the VCS) the files which I > need to edit.=C2=A0 Then, as I work, I type C-x 4 a and describe the chan= ges > being made to each function.=C2=A0 Finally, I check in the changes made t= o > those locked files, and update ChangeLog. >=20 > 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. Hmm, it seems it's an SVN workflow, because in git or Mercurial you can't l= ock file. I didn't have experience of working with SVN (fortunately, from what = I can tell), but I think if I had to work with it I would use `git-svn`. Anyway, I kind of wanted to see a commit you have troubles adding a title f= or. Judging by your first message here it's the same situation with commits to Emacs, so you can drop some commit hash for example. I kind of can speculat= e based on the general description of this SVN workflow, but it may be more productive to look at specific cases where such problem arises.