[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#52420: admin/release-branch.txt: move NEWS in single commit
|
From: |
Stefan Kangas |
|
Subject: |
bug#52420: admin/release-branch.txt: move NEWS in single commit |
|
Date: |
Sat, 11 Dec 2021 11:19:23 +0100 |
Eli Zaretskii <eliz@gnu.org> writes:
> I think we should modify admin.el to use "git mv" and commit that
> (after prompting), instead of calling rename-file etc. that it does
> today. IOW, there should be no need to do the above manually.
Yes, that sounds better.
- bug#52420: admin/release-branch.txt: move NEWS in single commit, Stefan Kangas, 2021/12/10
- bug#52420: admin/release-branch.txt: move NEWS in single commit, Eli Zaretskii, 2021/12/11
- bug#52420: admin/release-branch.txt: move NEWS in single commit,
Stefan Kangas <=
- bug#52420: admin/release-branch.txt: move NEWS in single commit, Stefan Kangas, 2021/12/26
- bug#52420: admin/release-branch.txt: move NEWS in single commit, Eli Zaretskii, 2021/12/27
- bug#52420: admin/release-branch.txt: move NEWS in single commit, Stefan Kangas, 2021/12/27
- bug#52420: admin/release-branch.txt: move NEWS in single commit, Eli Zaretskii, 2021/12/27
- bug#52420: admin/release-branch.txt: move NEWS in single commit, Stefan Kangas, 2021/12/27
- bug#52420: admin/release-branch.txt: move NEWS in single commit, Eli Zaretskii, 2021/12/27
- bug#52420: admin/release-branch.txt: move NEWS in single commit, Stefan Kangas, 2021/12/27