-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
admin/make-release.sh: automate release creation #74
admin/make-release.sh: automate release creation #74
Conversation
1d02ff8
to
62926b6
Compare
Please ignore the typo in the branch name 🙏 ... |
62926b6
to
c87fe3e
Compare
c87fe3e
to
215afd3
Compare
3cb3cba
to
b9539df
Compare
b9539df
to
4105629
Compare
This does the absolute bare minimum to produce a release. This logic best resembles the expectations for legacy (pre-0.22) releases of ATF. Various files are omitted as they are not required in order to build from a full `autoreconf`'ed source distribution. Signed-off-by: Enji Cooper <ngie@FreeBSD.org>
4105629
to
34bb903
Compare
looks good, same comments as in freebsd/kyua#252 |
@emaste : please note that I used a fixup commit here to ease review, so this will need to be squashed before merge. It's a practice I want to get into doing more because it makes reviews easier for reviewers. |
TIL: rebase merges with |
* admin/make-release.sh: automate release creation This does the absolute bare minimum to produce a release. This logic best resembles the expectations for legacy (pre-0.22) releases of ATF. Various files are omitted as they are not required in order to build from a full `autoreconf`'ed source distribution. Signed-off-by: Enji Cooper <ngie@FreeBSD.org>
This does the absolute bare minimum to produce a release.
This logic best resembles the expectations for legacy (pre-0.22) releases
of ATF.
Various files are omitted as they are not required in order to build
from a full
autoreconf
'ed source distribution.