git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David Symonds" <dsymonds@gmail.com>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How it was at GitTogether'08 ?
Date: Fri, 7 Nov 2008 21:08:27 -0800	[thread overview]
Message-ID: <ee77f5c20811072108o21f97c97i8174f4f7ecd67030@mail.gmail.com> (raw)
In-Reply-To: <200811080254.53202.jnareb@gmail.com>

On Fri, Nov 7, 2008 at 5:54 PM, Jakub Narebski <jnareb@gmail.com> wrote:

Here's my thoughts on some of these talks.

> Mon, Oct 27, 2008
> -----------------
> * Dscho: Contributing with Git
>  http://www.youtube.com/watch?v=j45cs5_nY2k

It was a good intro, but I was expecting a few more non-GitTogether
people. We had quite a large room, but there was only about a dozen
other people who came along. I don't know whether that was the fault
of the timing, lack of advertising, or a lack of interest.

> * Junio: Git Chronicle
>
>  blog: Junio went though a sort of statistical history of the Git project
>  that was fascinating (turns out there are still about 220 lines of code
>  still around from Linus original first commit).

This was really interesting. It would be great to put this on a
general web page instead of in a PDF.

> * Petr: Renames Again and Again and Again
>
>  IRC: detection of wholesame renames of directories (WIP) and '--follow'
>  limitation were mentioned, but outcome is unclear; pasky plans to hack
>  together some patch implementing explicit renames hinting

One thing I didn't get around to bringing up: one of the benefits of
diff-time rename detection that is often touted is that algorithms can
improve over time. Do folk here know whether that has actually
happened recently, in a general way? Do people actually expect major
improvements in the future?

> * Tom: GitHub
>
>  IRC: a tour, some history, and insight into how it works; some nice
>  gimmicks, such as "gist" (a git backed pastebin), or like network graphs
>  (look graphically at forks of a repository).
>
>  blog: Tom got to demonstrate GitHub and Gist to the group, most of whom
>  are very command line oriented and had not used either before.

The demo of iGitHub (an iPhone app that can act as a clone/push
target) looked really cool, if it can get further development. It
could potentially be really handy for travellers who could push to
their iPhone, and then push from there to an internet server.

> * Scott: Linkable Library
>
>  blog: got to talk about the need for a linkable git library
>
>  http://thread.gmane.org/gmane.comp.version-control.git/99608

It's good to see this starting to get wider traction. I think we
discussed that there could be benefits to git itself, beyond just
helping other programs access git repositories faster than fork/exec.

> * Sam: perl.git
>
>  blog: Sam demonstrated the work he went through to import 20 years of Perl
>  history into the git repository that the Perl team is just now finishing
>  transitioning to from Perforce.
>
>  http://utsl.gen.nz/talks/perl-history/slides/

It was very cool to see old-school email addresses like <isis!aburt>
in git, handled just fine.

> * Tim: Git as a Media Repository
>  http://www.thousandparsec.net/~tim/media+git.pdf

This has kicked off some mailing list discussion; I think this can be
a major weak point for git, since checking out only a subtree (and
only the latest revision) is the common SVN way, which copes with
media repositories and the like just fine.


> * JH: $$$ discussion
>
>  IRC: It was about the Google Summer of Code 2008 mentor money. It was
>  decided (given most of the mentors were there) to use it to help a few
>  folks cover their travel expenses to the GitTogether. Most folks actually
>  had their costs covered by their employer (yay for some big companies!)
>  but a few paid out of pocket, so we are helping them defray it a bit. and
>  the rest is being used to order and distribute some git t-shirts.

Yes, how are the t-shirts going? I seem to remember JH had volunteered
to do the logistics there.


Dave.

  parent reply	other threads:[~2008-11-08  5:10 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-08  1:54 How it was at GitTogether'08 ? Jakub Narebski
2008-11-08  3:41 ` Johan Herland
2008-11-08 14:17   ` Jeff King
2008-11-08  5:08 ` David Symonds [this message]
2008-11-08 15:31   ` Jakub Narebski
2008-11-09 15:36     ` Kai Blin
2008-11-09 16:31       ` Jakub Narebski
2008-11-09 18:55         ` Kai Blin
2008-11-10  9:30           ` Large media in git (was: How it was at GitTogether'08)? Jakub Narebski
2008-11-10 10:13             ` Kai Blin
2008-11-10  9:58           ` How it was at GitTogether'08 ? Johannes Schindelin
2008-11-10 10:08             ` Kai Blin
2008-11-10 12:09               ` Johannes Schindelin
2008-11-10 10:38     ` Johannes Schindelin
2008-11-10 11:36       ` Jakub Narebski
2008-11-09 11:49 ` Jakub Narebski
2008-11-09 16:52   ` Steven Grimm
2008-11-09 17:54     ` Jakub Narebski
2008-11-09 18:58     ` Robin Rosenberg
2008-11-09 19:55       ` Shawn O. Pearce
2008-11-09 21:58         ` Steven Grimm
2008-11-09 23:52           ` Jakub Narebski
2008-11-11 22:05             ` Jonas Fonseca
2008-11-11 23:26               ` Johannes Schindelin
2008-11-09 19:54   ` Shawn O. Pearce
2008-11-09 22:03     ` Jakub Narebski
2008-11-10  3:32   ` Tim Ansell
2008-11-09 23:32 ` Jean-Luc Herren
2008-11-11 21:35 ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ee77f5c20811072108o21f97c97i8174f4f7ecd67030@mail.gmail.com \
    --to=dsymonds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).