On Wed, Mar 02, 2011 at 11:40:32AM -0500, Jeff King wrote:
> It's sometimes useful to get a list of files in a tree along with the
> last commit that touched them. This is the default tree view shown on
> github.com...
A note on the motivation for this patch.
Some of you may already know this, but I started working full-time for
GitHub in January, working specifically on git. Most of it is just doing
the same general git work I've been doing; obviously GitHub has a vested
interest in git being awesome, and this gives me time to make it more
so.
I'm also working on changes that are going to be useful to large service
providers like GitHub more than other people. My plan is to open-source
those changes by putting them in a form that's useful to other git users
and submitting them as patches to the list. This is the first example,
but I have one or two more so far (GitHub actually runs a surprisingly
stock git).
I wanted to mention it here because:
1. GitHub is paying money for git development, which I think is cool
and they deserve some credit. Having more git time, I'm hoping to
tackle some of the long-standing issues that I have queued up
(e.g., I'll probably be working on multi-file follow and better
support for large binary files in the near future).
2. I want to be very open about the background behind my patches. I
think the list more-or-less operates on a per-patch meritocracy,
so in theory the patches should stand on their own or not. But as a
long-time contributor, I think it's best to be honest about the
fact that my motivations aren't _just_ scratching my own itch
anymore.
I have more or less full autonomy with respect to how I spend my
time, so there will still be a lot of itch-scratching. And if
something is junk or not useful to non-GitHub users, I won't waste
your time with it. So I think in general there won't be any change
in the usefulness of my patches. But being open about it lets you
choose how many grains of salt to take my patches with. :)
-Peff
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html