11 Commits (8507c2f8564b709bb6a3cc86e9599f6129f45c8e)

Author	SHA1	Message	Date
Tom Lane	80491a1983	Add 9.2 branch to git_changelog's list.	14 years ago
Bruce Momjian	7490c48f1e	Mark git_changelog examples with the proper executable names.	14 years ago
Bruce Momjian	f33fe47a91	Add comments suggesting usage of git_changelog to generate release notes.	14 years ago
Bruce Momjian	993ce4e6c9	Add options to git_changelog for use in major release note creation: ... --details-after --master-only --oldest-first	14 years ago
Tom Lane	7299778a95	Improve git_changelog's handling of inconsistent commit orderings. ... Use the CommitDate not the AuthorDate, as the former is representative of the order in which things went into the main repository, and the latter isn't very; we now have instances where the AuthorDate is as much as a month before the patch really went in. Also, get rid of the "commit order inversions" heuristic, which turns out not to do anything very desirable. Instead we just print commits in strict timestamp order, interpreting the "timestamp" of a merged commit as its timestamp on the newest branch it appears in. This fixes some cases where very ancient commits were being printed relatively early in the report.	14 years ago
Tom Lane	2ed81ebfaf	Add REL9_1_STABLE to the set of branches tracked by git_changelog.	15 years ago
Tom Lane	bf429cebd0	Improve git_changelog as per discussion with Robert Haas. ... 1. Resurrect the behavior where old commits on master will have Branch: labels for branches sprouted after the commit was made. I'm still dubious about this mode, but if you want it, say --post-date or -p. 2. Annotate the Branch: labels with the release or branch in which the commit was publicly released. For example, on a release branch you could see Branch: REL8_3_STABLE Release: REL8_3_2 [92c3a8004] 2008-03-29 00:15:37 +0000 showing that the fix was released in 8.3.2. Commits on master will usually instead have notes like Branch: master Release: REL8_4_BR [6fc9d4272] 2008-03-29 00:15:28 +0000 showing that this commit is ancestral to release branches 8.4 and later. If no Release: marker appears, the commit hasn't yet made it into any release. 3. Add support for release branches older than 7.4. 4. The implementation is improved by running git log on each branch only back to where the branch sprouts from master. This saves a good deal of time (about 50% of the runtime when generating the complete history). We generate the post-date-mode tags via a direct understanding that they should be applied to master commits made before the branch sprouted, rather than backing into them via matching (which isn't any too reliable when people used identical log messages for successive commits).	15 years ago
Tom Lane	899beb7894	Still more tweaking of git_changelog. ... 1. Don't assume there's only one candidate match; check them all and use the one with the closest timestamp. Avoids funny output when someone makes several successive commits with the same log message, as certain people have been known to do. 2. When the same commit (with the same SHA1) is reachable from multiple branch tips, don't report it for all the branches; instead report it only for the first such branch. Given our development practices, this case arises only for commits that occurred before a given branch split off from master. The original coding blamed old commits on *all* the branches, which isn't terribly useful; the new coding blames such a commit only on master.	15 years ago
Tom Lane	30d2e10058	Fix some more bugs in git_changelog. ... 1. Don't forget the last (oldest) commit on the oldest branch. 2. When considering which commit to print next, if two alternatives have the same "distortion" score (which is actually the normal case, since generally the "distortion" is 0), then choose the later timestamp to print first. I don't know where Robert got the idea to ignore timestamps and sort by branch age, but it wasn't a good idea: the resulting ordering of commits was just plain bizarre anywhere that some branches had many fewer commits than others, which is the typical situation for us.	15 years ago
Tom Lane	901a5a786f	Minor improvements to git_changelog. ... Avoid depending on Date::Calc, which isn't in a basic Perl installation, when we can equally well use Time::Local which is. Also fix the parsing of timestamps to take heed of the timezone. (It looks like cvs2git emitted all commit timestamps with zone GMT, so this refinement might've looked unnecessary when looking at converted data; but it's needed now.) Fix parsing of message bodies so that blank lines that may or may not get emitted by "git log" aren't confused with real data. This avoids strange formatting of the oldest commit on a branch. Check child-process exit status, so that we actually notice if "git log" fails, and so that we don't accumulate zombie children.	15 years ago
Tom Lane	ce1dcd468f	Rename git_topo_order -> git_changelog, per discussion.	15 years ago
Robert Haas	1b984d43e5	git_topo_order script, to match up commits across branches. ... This script is intended to substitute for cvs2cl in generating release notes and scrutinizing what got back-patched to which branches. Script by me. Support for --since by Alex Hunsaker.	16 years ago