1 |
Fernando Rodriguez wrote: |
2 |
> On Saturday, August 29, 2015 10:48:16 AM Dale wrote: |
3 |
>> Todd Goodman wrote: |
4 |
>>> * Philip Webb <purslow@××××××××.net> [150828 18:35]: |
5 |
>>>> 150828 Rich Freeman wrote: |
6 |
>>>>> To really appreciate git you should understand git objects |
7 |
>>>>> and their references, what a commit, tree, and blob are. |
8 |
>>>>> Also, the whole copy-on-write concept and content-hashing concept. |
9 |
>>>>> I used to think git looked really complicated until I sat |
10 |
>>>>> through a 1 hr talk that focused mostly on the data model. |
11 |
>>>>> Once you understand the data model, you understand everything. |
12 |
>>>>> That doesn't take a lot of time. It does take a moderate amount of time |
13 |
>>>>> learning the right things. They're not found in the manpages. |
14 |
>>>>> Like I said, beautiful design, horrible interface. |
15 |
>>>> So is there a Gentoo doc -- Wiki, presumably -- |
16 |
>>>> explaining to users -- users, not dev's or Git addicts -- |
17 |
>>>> the essentials of Git, so that they can readily update using it ? |
18 |
>>>> If so, I'm willing to see if I can use it ; |
19 |
>>>> if not, I would suggest it sb a top priority for dev's to write. |
20 |
>>> You don't *need* to know anything about git to update using it. |
21 |
>>> |
22 |
>>> Just change your /etc/portage/repos.conf/gentoo.conf as Rich outlined |
23 |
>>> (and move away your rsync'd /usr/portage or wherever your portage tree |
24 |
>>> goes.) |
25 |
>>> |
26 |
>>> Then when you emerge --sync (or emaint -A sync, etc.) it will sync via |
27 |
>>> git and emerge will work as always. |
28 |
>>> |
29 |
>>> Now if you want to do more or just want to learn more about git then |
30 |
>>> that's different. |
31 |
>>> |
32 |
>>> Todd |
33 |
>>> |
34 |
>>> |
35 |
>>> |
36 |
>> |
37 |
>> I think what we are talking about is viewing things like the changelogs |
38 |
>> and such, which are currently not synced with the tree. Or did we |
39 |
>> change to some other topic and I missed it? I tracked back to Alan |
40 |
>> Mackenzie's split of this thread |
41 |
>> . |
42 |
>> Dale |
43 |
>> |
44 |
>> :-) :-) |
45 |
>> |
46 |
> It's probably easier to do this: |
47 |
> |
48 |
> # cd /usr/portage |
49 |
> # rm -r * |
50 |
> # git clone <repo-uri> . |
51 |
> |
52 |
> Then do the repos.conf changes. That way you don't have to worry about portage |
53 |
> doing a shallow clone. If you already did it then just unshallow it as Rich |
54 |
> pointed. Then to view the logs just: |
55 |
> |
56 |
> #cd /usr/portage/cat/pkg |
57 |
> #git log . |
58 |
> |
59 |
> Then 'git show <first few digits of commit hash>' to view a commit diff. You can |
60 |
> use git use dev-vcs/tig if you find it easier though I thought it was pretty |
61 |
> useless so it only lasted about 10 secs. in my system. |
62 |
> |
63 |
> So basicly the only change is that instead of: |
64 |
> |
65 |
> # less ChangeLog (or whatever you use to read logs) |
66 |
> |
67 |
> You'll do: |
68 |
> |
69 |
> # git log . |
70 |
> |
71 |
> |
72 |
|
73 |
|
74 |
Actually, I use eix-sync to sync my tree. However I do it, I want it |
75 |
done within the usual setup and commands. Given the bumps we've already |
76 |
seen, I'm not wanting to change that just yet. Let the devs work out |
77 |
some of the kinks first. |
78 |
|
79 |
Oh, I use Kwrite to read the changelogs. If I'm stuck in a console, |
80 |
nano, head or cat works. Well, it did in the past anyway. May not now tho. |
81 |
|
82 |
Dale |
83 |
|
84 |
:-) :-) |