I have had a few emails about "where is the latest dtrace?" despite
it being posted on every web page I maintain, and provide the lowest common
denominator - tarballs! Such a nice word :-)
People ask, cant I do "git"? Well...simple answer is "no". There
is a unmaintained(?) dtrace github page, but it wasnt set up by me,
but an enthusiastic supporter.
I can understand people either wanting to track changes or make
So, I am opening up the conversation to people: Just how badly can
I damage GIT ?!
I have recently started using GIT and automating the commits at home,
but I am lacking an understanding of git and how to cope with complexity.
Heres the deal. In theory I have two main machines - a server,
rarely switched on, but the "master", and my laptop, where I do most
of my work -- manually syncing changes (not just dtrace, but
for CRiSP and other things) across the machines.
I set up git on my master and laptop ($HOME/git) and use symlinks in
my source code dirs so that the git repository is in its own tree.
Previously, I would just create periodic tarballs as snapshots -
which are mostly fine, but not necessarily synchronised to the sync points.
I rsync my laptop/master git repositories - probably a bad thing. Is it?
So, if an external facing git repository is available, what does it
Q1: I can sync to the external repository from my internal, and stop doing
tarballs? (Or keep doing both).
Q2: Who can touch the git repo? Presumably whoever I permission, or, is
it a free-for-all?
Q3: Assuming its a trusted circle of people, then how do I sync
from the repo back to my local git repo?
I really want to review what people do and likely not
accept some contributions or recode them to fit in with my "style".
I dont want to be a Linus/Git-meister (but will if need be - if it
helps the greater good).
So, educate me or be gentle with me.
(I am busy adding some new features to CRiSP and fcterm to show
outline grids whilst editing, and when I finish this, I may go back to
Dtrace and start to remember "What was I planning to do next").