summaryrefslogtreecommitdiff
path: root/bsd/radeon
diff options
context:
space:
mode:
authorDave Airlie <airlied@linux.ie>2004-07-29 12:49:54 +0000
committerDave Airlie <airlied@linux.ie>2004-07-29 12:49:54 +0000
commitb1cf4ca7e540bcf28beaf3f5a70915a810a75b1b (patch)
treece8912e526b19dfbb4fc523b1975ff18fb66ce62 /bsd/radeon
parent0b02bf9d45b70af3b7e236526143c7b78a6fca8b (diff)
change to agp not pci ... still not working
Diffstat (limited to 'bsd/radeon')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-18 20:40:27 +0000
end with a message of the form: ============================================= libdrm-X.Y.Z archives ready for distribution: libdrm-X.Y.Z.tar.gz libdrm-X.Y.Z.tar.bz2 ============================================= Make sure that the version number reported by distcheck and in the tarball names matches the number you bumped to in configure.ac. 6) Commit the configure.ac change and make an annotated tag for that commit with the version number of the release as the name and a message of "libdrm X.Y.Z". For example, for the 2.4.16 release the command is: git tag -a 2.4.16 -m "libdrm 2.4.16" 7) Push the commit and tag by saying git push --tags origin master assuming the remote for the upstream libdrm repo is called origin. 6) Use the release.sh script from the xorg/util/modular repo to upload the tarballs to the freedesktop.org download area and create an annouce email template. The script takes three arguments: a "section", the previous tag and the new tag we just created. For 2.4.16 again, the command is: ../modular/release.sh libdrm 2.4.15 2.4.16 This copies the two tarballs to freedesktop.org and creates libdrm-2.4.16.announce which has a detailed summary of the changes, links to the tarballs, MD5 and SHA1 sums and pre-filled out email headers. Fill out the blank between the email headers and the list of changes with a brief message of what changed or what prompted this release. Send out the email and you're done!