From: Bart Schaefer <schaefer@brasslantern.com>
To: Mailing-list zsh-workers <zsh-workers@zsh.org>
Subject: Re: GH:zsh-users/zsh-completions.
Date: Wed, 18 Oct 2017 18:09:01 -0700 [thread overview]
Message-ID: <171018180901.ZM19235@torch.brasslantern.com> (raw)
In-Reply-To: <21335.1508343802@thecus.kiddle.eu>
On Oct 18, 6:23pm, Oliver Kiddle wrote:
}
} We preserved the ChangeLog in its existing form when migrating from CVS
} largely so that we were changing as little as possible. But we have git
} log. All new ChangeLog entries can be autogenerated
This is so appealing in theory and yet so horrible (IMO) in practice.
Git log format does not lend itself to this [*] and its immutability
makes it impossible to correct errors (of which we have plenty) or to
fix mis-attribution when e.g. one of the developers is committing on
behalf of some other contributor who should get credit.
[*] Yes, I know you can use formats to present the log in a whole lot
of flexible ways. But the one thing you can't change is what info is
stored by git in the first place, to which to apply those formats.
--
Barton E. Schaefer
next prev parent reply other threads:[~2017-10-19 1:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7240.1507973844@thecus.kiddle.eu>
2017-10-14 14:44 ` GH:zsh-users/zsh-completions Julien Nicoulaud
2017-10-14 16:49 ` GH:zsh-users/zsh-completions Eric Cook
2017-10-16 14:29 ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-10-16 15:11 ` GH:zsh-users/zsh-completions Peter Stephenson
2017-10-16 15:24 ` GH:zsh-users/zsh-completions Bart Schaefer
2017-10-16 15:42 ` GH:zsh-users/zsh-completions Peter Stephenson
2017-10-16 17:49 ` GH:zsh-users/zsh-completions gi1242+zsh
2017-10-17 21:09 ` GH:zsh-users/zsh-completions Joey Pabalinas
2017-10-18 16:23 ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-10-19 1:09 ` Bart Schaefer [this message]
2017-10-19 4:03 ` GH:zsh-users/zsh-completions Aaron Schrab
2017-10-19 5:24 ` GH:zsh-users/zsh-completions Bart Schaefer
2017-11-01 23:33 ` ChangeLogs (Re: GH:zsh-users/zsh-completions.) Oliver Kiddle
2017-11-01 23:46 ` Bart Schaefer
2017-11-02 20:09 ` Oliver Kiddle
2017-10-19 1:31 ` GH:zsh-users/zsh-completions Joey Pabalinas
2017-10-19 14:37 ` GH:zsh-users/zsh-completions Daniel Shahaf
2017-10-30 23:38 ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-11-01 16:35 ` GH:zsh-users/zsh-completions Daniel Shahaf
2017-11-01 22:58 ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-10-16 23:00 ` GH:zsh-users/zsh-completions Bart Schaefer
2017-10-16 20:04 ` GH:zsh-users/zsh-completions Daniel Shahaf
2017-10-17 7:53 ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-10-17 8:41 ` GH:zsh-users/zsh-completions Peter Stephenson
2017-10-16 15:26 ` GH:zsh-users/zsh-completions gi1242+zsh
2017-10-17 9:35 ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-10-19 18:25 ` GH:zsh-users/zsh-completions Daniel Tameling
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=171018180901.ZM19235@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).