Re: gittogether session notes

On Mon, Nov 1, 2010 at 3:32 PM, Shawn O. Pearce [off-list ref] wrote:

Jeff King [off-list ref] wrote:

quoted

On Fri, Oct 29, 2010 at 12:26:15PM -0700, Jakub Narebski wrote:

quoted

Below there are proposed talks which either weren't presented, or lack
notes / slides.
* Hudson and Gerrit integration

Brad Larson talked about Hudson, and had slides. I don't seem to have an
email address for him, though.

Brad, can you post your Hudson slides on the wiki?

I didn't have slides, just a live demo of Hudson running on my box
doing build tests of tools/gerrit from android.git.kernel.org.  I'll
take some screen shots and throw them into a presentation for
historical reference.  Should I email that to someone or ...?

Brad

quoted

quoted

* What's new on github: pull requests, git based wiki etc.

Tom talked about this, but there weren't any slides.  He just
presented the web site and described what he was showing.

quoted

quoted

* Git and Big Files

John Hawley and I talked about this a bit, it probably makes sense
to take Avery's bup work and start to formalize it within core Git.
But yea, we didn't ever get around to debating the merits of a new
"sequence" object type vs. defining a new variant of the current
tree mode and reusing the current tree walking support to link in
the segments of the huge file.

I think it really depends on what older versions of Git will
do.  If older Git versions would accept a different tree mode
(e.g. '040001') and treat them as normal trees, we could at least
use older Git servers for push/pull/fsck/gc without breaking the
repository.  But doing a checkout would produce a directory of
segments, and updating a segment would break the directory mode.
But I suspect older gits will choke on that tree mode.

quoted

quoted

* git log -L demo, combination of log and blame

Thomas did this, but it was mostly just showing off "-L".

And this is pretty cool too.  I was pretty impressed by the flag.

quoted

quoted

* RefInsteadOf (discussion)

RefInsteadOf turned out to be a non-discussion.  I asked the SEMC
guys what they wanted... and it turns out its already handled
somewhere else and they didn't realize it.  They just needed to
use the fetch refspec in .git/config correctly.  :-)

quoted

quoted

* git-always-on

This was the Qualcomm guys presenting how they use DRBD to keep
git in sync on multiple machines and implement quick fail-over when
there is a problem with the primary.

--
Shawn.