crowdsourcing an interview on git

[Paul W. Frields]

On Wed, Apr 01, 2015 at 10:49:57AM -0600, Kevin Fenzi wrote:
> On Tue, 31 Mar 2015 16:48:17 -0400
> Matthew Miller <mattdm at fedoraproject.org> wrote:
> 
> > Hi everyone! Linux Foundation is running a series on Git for its 10th
> > anniversary. They asked me a few questions, and I thought it might be
> > even better to get a community answer from the whole infrastructure
> > team. So, if you have anything interesting to say to any of these, say
> > it, and I'll wrap up the responses into a unified Fedora Whole. I need
> > to respond by Friday.
> > 
> > * Why does Fedora use Git?
> 
> It's known by most all developer/free software types these days, it's
> distributed and it's got a lot of docs and folks that can help with
> issues. 
> > 
> > * What makes Git such a great tool?
> 
> For simple things/workflows it's pretty simple. 

Because it's distributed, you can be productive on a plane or at other
locations without a network.

> > * How many developers do you have collaborating on git?
> 
> I guess that depends on what the question means by "you" here. ;) 
> 
> We have had 45 people commit at one time or another to our ansible
> repo, and 163 to our old puppet repo. 
> 
> There's 1633 people in the fedora packager group and 19857 package
> repos. (But some of those are dead.packaged). 
> 
> > * How much do you personally use it? (estimates are great)
> 
> Many times a day. 
> 
> > * What's Fedora's most active git repo right now and why?
> 
> Thats hard to say, we don't have a central place for all of them... 
> http://pkgs.fedoraproject.org/cgit/?s=idle
> I suspect kernel gets updates most days. 
> The infrastructure ansible repo gets updates most days. 
>  
> > * What is your favorite pro tip for using git?
> 
> Always run 'git status' and 'git diff' before commiting/pushing. That
> can show you that you have unrelated other changes you might not want
> to push. 

If you make really bad mistakes, you can use 'git reflog' to reverse
even egregious issues.

Also, 'git rebase -i' is great for times you forgot to keep your
commits focused on the topic at hand.  You can merge, split up, or
edit diffs to make sure your commits are useful when you come back to
them weeks or months later.

-- 
Paul W. Frields                                http://paul.frields.org/
  gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233  5906 ACDB C937 BD11 3717
  http://redhat.com/   -  -  -  -   http://pfrields.fedorapeople.org/
    The open source story continues to grow: http://opensource.com