Re: How it was at GitTogether'08 ?
- From
David Symonds <dsymonds@gmail.com>
- Date
- Nov 8, 2008, 05:08 UTC
- Message-ID
- <ee77f5c20811072108o21f97c97i8174f4f7ecd67030@mail.gmail.com>
- 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.
Show 5 quoted lines
> * 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.
Show 5 quoted lines
> * 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?
Show 8 quoted lines
> * 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.
Show 5 quoted lines
> * 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.
Show 7 quoted lines
> * 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.
Show 8 quoted lines
> * 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.