Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit58ba7e5

Browse files
Add .abi-compliance-history to back-branches.
This file was previously added to v18 by commitsa72f7d9 and93fb76c. Unlike the v18 version of the file, the back-branchversions set the original baseline point to the most recent ABIbreak documented in the git commit history. While we'd ordinarilyset it to something just before the .0 release, we're unlikely toact upon ABI breaks in released minor versions, so it doesn't seemworth the trouble to construct a comprehensive history.Discussion:https://postgr.es/m/aPfDOD6F4FaJJd7M%40nathanBackpatch-through: 13-17
1 parent0a358eb commit58ba7e5

File tree

1 file changed

+30
-0
lines changed

1 file changed

+30
-0
lines changed

‎.abi-compliance-history‎

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
# Reference point for ABI compliance checks
2+
#
3+
# This file lists commits on the current branch that break ABI compatibility in
4+
# ways that have been deemed acceptable (e.g., removing an extern function with
5+
# no third-party uses). The primary intent of this file is to control the ABI
6+
# compliance checks on the buildfarm, but it also serves as a central location
7+
# to document the justification for each.
8+
#
9+
# In general, entries should be added reactively after an abi-compliance-check
10+
# buildfarm failure. It is important to verify the details of the breakage
11+
# match expectations, as the first entry listed will become the updated ABI
12+
# baseline point.
13+
#
14+
# Add new entries by adding the output of the following to the top of the file:
15+
#
16+
# $ git log --pretty=format:"%H%n#%n# %s%n# %cd%n#%n# <ADD JUSTIFICATION HERE>" $ABIBREAKGITHASH -1 --date=iso
17+
#
18+
# Be sure to replace "<ADD JUSTIFICATION HERE>" with details of your change and
19+
# why it is deemed acceptable.
20+
21+
983b3636259b1502121cbae99d8a2f0d0515d87d
22+
#
23+
# Fix re-distributing previously distributed invalidation messages during logical decoding.
24+
# 2025-06-16 17:35:50 -0700
25+
#
26+
# This is the original ABI baseline point for REL_14_STABLE. The first entry
27+
# would ordinarily point to something just before the .0 release, but this file
28+
# was first added in October 2025, and we're unlikely to act upon ABI breaks in
29+
# released minor versions, so we've chosen to truncate the ABI history to start
30+
# with the most recent ABI break documented in the git commit history.

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp