1 |
> On 05/26/2016 04:32 AM, Peter Humphrey wrote: |
2 |
> Aye, there's the rub. Git is a closed book to me at the moment. |
3 |
|
4 |
Hello, |
5 |
|
6 |
I started a new thread for (2) reason. |
7 |
1. The original thread does not show up in my gmane, as it was |
8 |
down for a few days. |
9 |
|
10 |
2. I think 'subject drift' warrants a new thread. Anyway recap:: |
11 |
|
12 |
|
13 |
You are not alone Peter. In fact there are so many git documents, howto |
14 |
and such that every time I 'dive in' I mostly get a mess. Thankfully, |
15 |
I keep duplicates of the codes in an old fashion directory tree |
16 |
structure;(circa 35 years now). |
17 |
|
18 |
Better yet MO writes:: |
19 |
<snip> |
20 |
|
21 |
You'll spend a while getting used to git, there's no way around it. You |
22 |
just have to pick a project and force yourself to use git all day. All |
23 |
of the commands have the wrong names: |
24 |
|
25 |
* Want to check out a repository? There's `git checkout`, but that's |
26 |
not what it does. You want `git clone`. |
27 |
|
28 |
* Want to start a new branch? There's `git branch`, but what you |
29 |
actually want is `git checkout`. |
30 |
|
31 |
* Want to reset the modifications you've made to a file? There's |
32 |
`git reset`, but what you really want is `git checkout`. |
33 |
|
34 |
* Want to merge your changes with upstream? There's `git merge`, |
35 |
but chances are, you want `git pull --rebase`. |
36 |
|
37 |
* Want to commit a new file? There's `git commit`, but it won't work. |
38 |
|
39 |
...and so on. |
40 |
|
41 |
That said, after my bicycle, git is probably the most useful piece of |
42 |
technology I use on a daily basis. All of the time I spent banging my |
43 |
head on my desk turned out to be well worth it. So, don't despair too much. |
44 |
|
45 |
<end/snip> |
46 |
|
47 |
|
48 |
which is GREAT! We just need more like this collected into the |
49 |
gentoo-wiki-gentoo-git(hub)-handbook. |
50 |
|
51 |
|
52 |
If fact maybe what we need is some GENTOO git/github guide collection that |
53 |
ramps ups novices to some functional level with git and github via a well |
54 |
defined pathway. Maybe that has already been documented on the irc channels |
55 |
used by the 'proxy-maintainers'? Dunno..... |
56 |
|
57 |
But since git/hub is so intertwined now at gentoo, I'd surely appreciate a |
58 |
GENTOO(git/hub)handbook so those of us not up to dev-status have a |
59 |
functional guide that we can read and follow, up to a certain level. Maybe |
60 |
that level is joining proxy-maintainer's club; then dev status. |
61 |
|
62 |
|
63 |
Rote responses to the effect of 'go learn git/hub' I find is like learning |
64 |
to cliff dive from 75' without first learning from a 1 meter spring-board. |
65 |
It's just dysfunctional. The old CVS stuff was self explanatory and easy to |
66 |
pick up. |
67 |
|
68 |
I do follow the recent devmanual efforts and EAPI6 and it seems to me that |
69 |
the level of senior dev input to guide the other devs in those efforts is |
70 |
bearing lots of fruit, as we (the user community) explore proxy-maintenance |
71 |
and such 'step-up' pathways. If the devs want more proxy and devs to join, |
72 |
making that pathway well defined goes a long way to encouraging folks, imho. |
73 |
|
74 |
|
75 |
So what do others think, do we need a git/hub handbook right after the |
76 |
gentoo-install-handbook, full of tips and recipes for gentoo git_noobs? |
77 |
|
78 |
|
79 |
comments welcome, |
80 |
James |