On Mon, Nov 29, 2021 at 11:43 AM Peter Humphrey <[email protected]> wrote: > > On Monday, 29 November 2021 16:32:45 GMT Rich Freeman wrote: > > On Mon, Nov 29, 2021 at 11:17 AM Peter Humphrey > <[email protected]> wrote: > > > # (cd /var/db/repos/gentoo/sys-devel/gcc && git whatchanged) > > > > You'd get just as much output from git log - you didn't restrict the > > output so it ran on the entire repository. The current working > > directory has no impact on the function of either git log or git > > whatchanged. > > See what I mean about counter-intuitive?
You won't get any arguments from me that git is not a very refined piece of software. The other glaring flaw is inconsistencies in command line options between various subcommands. It is a beautiful concept, with a rough implementation. > > > You could append a . to just run git whatchanged on the current > > directory. I run "git whatchanged ." all the time. > > Thanks. I will. But how do I find the real change log of a package? The sort > of > stuff I used to include in a software release bulletin when I was running the > show. What has changed, and why? What fault reports have been closed? What > new behaviour can be expected? If there are any gentoo bugs resolved by a commit they're likely to show up in the log (or with whatchanged), unless you ask for a oneline version which will only show the first line of the log. The bugs would include links but obviously you'd have to hunt down what they actually are. Usually if a commit fixes some sort of serious issue it is going to end up in the text of the commit description, especially if that were the only change. If it is a version bump and it happened to also update the EAPI or fix a URL or something minor that might not get mentioned. As far as upstream behavior changes goes, don't expect to see this in the commit log unless it is incredibly impactful, in which case you might get news (like some big ABI break in the toolchain or something). In general Gentoo does not really do handholding with release notes with upstream changes, or even provide more than a basic level of integration across packages. As was mentioned in another recent discussion, don't expect that the latest stable kernel is guaranteed to work with the latest stable zfs-kmod package, etc. A more release-based distro would be better equipped to do that but actually doing a serious job of upstream release notes would be a LOT of work. The Gentoo commit log is going to be more about changes in how something is packaged. Some are more detailed than others. I know I personally try to mention things like EAPI changes but I'm not sure that everybody does. Unfortunately since most changes create new revisions the diff capabilities of git tend to be limited in usefulness. -- Rich
