My friend git

[Leslie S Satenstein]

I rely on Dropbox for much of my temporary backups. I have rarely ever had 2 gigs of source for a single application, including some previous generations.  In a collaboration project for text, I use both svn and GIT.

 


 
Regards 

 Leslie

Mr. Leslie Satenstein
An experienced Information Technology specialist.
Yesterday was a good day, today is a better day,
and tomorrow will be even better.lsatenstein at yahoo.com
alternative: leslie.satenstein at gmail.com 
SENT FROM MY OPEN SOURCE LINUX SYSTEM.





>________________________________
> From: Pete Travis <me at petetravis.com>
>To: wb8rcr at arrl.net; For participants of the Documentation Project <docs at lists.fedoraproject.org> 
>Sent: Wednesday, August 21, 2013 2:56 AM
>Subject: Re: My friend git
> 
>
>On 08/20/2013 08:19 AM, John J. McDonough wrote:
>> Chris Wickert posted this link on Facebook:
>>
>> http://t.co/865gbg2S4o
>>
>> The biggest take-away from that page is hidden toward the bottom:
>>
>>   Here’s the golden rule of git: if you lose data but you checked
>>   it in somewhere, you can probably recover it. If you didn’t
>>   check it in, you probably can’t. So check in often!
>>
>> You've heard a lot of us say commit early and commit often - that's why.
>>
>> I use git for a LOT of my personal stuff.  It lets me go back easily
>> when I've shot myself in the foot (as I do often), and it also lets me
>> go off on several tangents all at once (yeah, scatterbrained).
>>
>> I have a "remote" repo on my LAN that I push to as often as I commit.
>> That way if I happen to be at a different computer I can just clone the
>> repo and have the same thing I had on the first computer, and if my
>> laptop should die, my important stuff is in the repo even between
>> backups.
>>
>> And not only that, when I have something I want to share with others, I
>> simply push my LAN remote repo to gitorious and my friends can follow
>> along.
>>
>> So get real friendly with git.  It isn't just one of those process
>> things you put up with for your guide, it is an amazing tool.
>>
>> --McD
>>
>>
>
>Good article! There are a few things in there I'll probably turn on.
>
>My git usage is prolific but fairly basic; etckeeper, pushing
>$HOME/.dotfiles to the fileserver, the occasional patch on github or
>gitorious.  I'm working on packaging a few things right now, and set up
>a git repo in ~/rpmbuild and branch for each package; having the commit
>log to track the reviews and using branches with $(git clean -xdf) to
>keep things orderly really helps. I use git to separate local
>development and production content for websites, and to push out to
>production - or at least I have that set up, for when I bother to push
>to production :P
>
>I like reading other writers' commit logs, too.  I learn new things, and
>keep track of what is being worked on. I don't *own* a guide, just pick
>up sections to contribute to on the fly, and it is much easier to
>contribute to a guide when I can see what the other writers are doing
>with it.
>
>
>-- 
>-- Pete Travis
>- Fedora Docs Project Leader
>- 'randomuser' on freenode
>- immanetize at fedoraproject.org
>
>
>-- 
>docs mailing list
>docs at lists.fedoraproject.org
>To unsubscribe:
>https://admin.fedoraproject.org/mailman/listinfo/docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/docs/attachments/20130821/f17d1af9/attachment-0001.html>