diff options
| author | gdt <gdt@pkgsrc.org> | 2007-07-28 12:23:17 +0000 |
|---|---|---|
| committer | gdt <gdt@pkgsrc.org> | 2007-07-28 12:23:17 +0000 |
| commit | ff5558bc4c5d943495ee3938823cd67d8d1e0917 (patch) | |
| tree | 34f951662a2ec9d9e8c1017b23d5e65602dcfab6 /chat | |
| parent | 8eae668606fba4dcb3b706be2bdbdd48a4ccf170 (diff) | |
| download | pkgsrc-ff5558bc4c5d943495ee3938823cd67d8d1e0917.tar.gz | |
Rationalize changes-entry and commit-changes-entry.
changes-entry now does cvs update (and cvs edit if needed), and adds
the line. This target will behave the same way (with extra CVS
traffic) if the file is up to date, and will be omre useful if
CHANGES-YYYY is not up to date.
commit-changes-entry depends on changes-entry and also commits. This
target has no behavior changes.
Rename _CCE_FOO variables to PKGSRC_CHANGES_FOO, and merge with
existing varables.
We may need a changes-entry-no-update, or a new name for what
changes-entry does now. Given how infrequently CHANGES-YYYY is up to
date when I want to add, I believe the new behavior will be welcome to
almost everyone.
Diffstat (limited to 'chat')
0 files changed, 0 insertions, 0 deletions