-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 11/02/2015 12:00 PM, Dale wrote: > Rich Freeman wrote: >> On Mon, Nov 2, 2015 at 1:08 AM, Dale <rdalek1...@gmail.com> >> wrote: >>> Then perhaps all this should have been worked out BEFORE >>> switching to github? >> We didn't switch to github. > > Then why are people saying to use git to look at the logs? I > don't want to use git. I liked being able to go to the tree and > look at the change logs when I needed to which is sometimes often. > Now, that is gone because it is somewhere else and people are > saying to use git to get them. Sounds like a switch to me. > > [snip] > >
As Ciaran has already said, git and GitHub are not the same thing. GitHub is a proprietary website for hosting repositories; git is the software written by Linus Torvalds that we use for revision control. You can still go to the tree and look at logs. If you're syncing using hasufell's git repo method (which has been great, btw; thanks hasufell), then you already have a copy of the git repo on your system. `cd` to the directory and you can do all sorts of stuff with `git log` to check out what's happened. Let's say I want to see what's happened with Firefox lately: git log -- www-client/firefox/ Bam, you'll get a complete log of the commits that have happened to *all* files in that directory. You can add `--oneline` to make it easier to scan through, too. If a specific commit stands out to you, you can use `git show <commit-id>` to get details on what that commit di d. For example, let's see what happened with a somewhat larger commit that happened about a month ago. Note that you don't need the complete commit ID; just enough so git finds a unique match. git show 3a8d9727 That'll show where Manifests were updated, variables changed in ebuilds, and so on. - --- So the workflow is basically `git log -- category/package/`, find a commit that looks interesting, then `git show commit-id` to look at what it did. It's actually much better than changelogs, imo. - -- Daniel Campbell - Gentoo Developer OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWN9g0AAoJEAEkDpRQOeFw/z8P/2tBVybg+ShZoOJtQkXL0ZZK eZg1REfydxifZlaaOl3FvfTSe4SkaAfvOoxKN97SivsKPI17uO0qPMfccevotbeX cVkOptLF6oVcSP9tGK59cV8NvPk6sI6PJkfY3VhAZnM7NAW5VDXEdnQMQDPg3C9C BNiUKYs+iOAZXOQta5FMNn/V833tJhUEdF5dNyw5JwWNMEAfuXfOfmqJ3Fdty7tz tIsdGVV22t6XiIeAdxI3QqNEzla+jeUauHGz69LsJMS68FCJfO6jUwioEuwwD+7c CkVBMB2aWogfHzcRIaJQ0ywMQaYRnhZTzT3BfijaQKi5vGVp69elywaMa9VFCkeo AKq+OQbzWzmTfUg9O6iKGPNi7dGyRS2U8Xn+8S6HD5hcIrgh052NZeRQ2YBe0DHg X0+dkjIBzMNiVC2NF7WCvfZ7YxjvrkKkR+IipLU9NxGMRcMHSMkFjvXotsfkRuO0 OPG34U4hEEsUjoWNw4/kfkC6+ISz4+KlITm9h40rJytuLkdcVyZNPZP1yBekWK31 wgMuLsaSg0w2D2zdr4aNN7eFba4tGRYPcRqq9cU6/dAyeKzvrnI4FTkjfGVrf2OX pSupy0bQY1bYT6MYiKCXG+jaE0IOzNakSlgl9c3JSUQgo3a7D0iwS7oB95X2B0gf S9or/fPUkcJC8o0dNdSz =X623 -----END PGP SIGNATURE-----
