On Saturday, August 29, 2015 10:48:16 AM Dale wrote: > Todd Goodman wrote: > > * Philip Webb <purs...@ca.inter.net> [150828 18:35]: > >> 150828 Rich Freeman wrote: > >>> To really appreciate git you should understand git objects > >>> and their references, what a commit, tree, and blob are. > >>> Also, the whole copy-on-write concept and content-hashing concept. > >>> I used to think git looked really complicated until I sat > >>> through a 1 hr talk that focused mostly on the data model. > >>> Once you understand the data model, you understand everything. > >>> That doesn't take a lot of time. It does take a moderate amount of time > >>> learning the right things. They're not found in the manpages. > >>> Like I said, beautiful design, horrible interface. > >> So is there a Gentoo doc -- Wiki, presumably -- > >> explaining to users -- users, not dev's or Git addicts -- > >> the essentials of Git, so that they can readily update using it ? > >> If so, I'm willing to see if I can use it ; > >> if not, I would suggest it sb a top priority for dev's to write. > > You don't *need* to know anything about git to update using it. > > > > Just change your /etc/portage/repos.conf/gentoo.conf as Rich outlined > > (and move away your rsync'd /usr/portage or wherever your portage tree > > goes.) > > > > Then when you emerge --sync (or emaint -A sync, etc.) it will sync via > > git and emerge will work as always. > > > > Now if you want to do more or just want to learn more about git then > > that's different. > > > > Todd > > > > > > > > > I think what we are talking about is viewing things like the changelogs > and such, which are currently not synced with the tree. Or did we > change to some other topic and I missed it? I tracked back to Alan > Mackenzie's split of this thread > . > Dale > > :-) :-) >
It's probably easier to do this: # cd /usr/portage # rm -r * # git clone <repo-uri> . Then do the repos.conf changes. That way you don't have to worry about portage doing a shallow clone. If you already did it then just unshallow it as Rich pointed. Then to view the logs just: #cd /usr/portage/cat/pkg #git log . Then 'git show <first few digits of commit hash>' to view a commit diff. You can use git use dev-vcs/tig if you find it easier though I thought it was pretty useless so it only lasted about 10 secs. in my system. So basicly the only change is that instead of: # less ChangeLog (or whatever you use to read logs) You'll do: # git log . -- Fernando Rodriguez
