git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
	Jeff King <peff@peff.net>, Petr Baudis <pasky@suse.cz>,
	Steven Grimm <koreth@midwinter.com>,
	Tim Ansell <mithro@mithis.com>
Subject: Re: How it was at GitTogether'08 ?
Date: Sun, 9 Nov 2008 12:49:39 +0100	[thread overview]
Message-ID: <200811091249.40735.jnareb@gmail.com> (raw)
In-Reply-To: <200811080254.53202.jnareb@gmail.com>

On Sat, 8 Nov 2008, Jakub Narębski wrote:

> GitTogether 2008, which took place October 27(Mon)-29(Wed), has ended more
> than week ago.  Therefore I'd like to ask you impressions (while it is still
> fresh) from GitTogether, describe talks which are not described below,
> correct wrong information in below, etc.
> 
> Please reply to this email while GitTogether is on front of your mind...

Still missing (neither video, nor slides, nor description, nor email)
are the following talks from GitTogether'08

 
> Talks at GitTogether 2008
> =========================
> 
> Mon, Oct 27, 2008
> -----------------
> * Jeff: Helping new contributors join
> * Shawn: JGit
 
> Tue, Oct 28, 2008
> -----------------
> * Jeff: What needs refactoring?
> * Lighting Round Talks
>   - Jeff: Portability autobuilders
>   - Petr: Quick TopGit introduction, problems, future plans
> * Steven: Life with git-svn

> Wed, Oct 29, 2008
> -----------------
+ What was the difference between "Tim: Large media in Git (Repeat)"
  from Wed, and earlier "Tim: Git as a Media Repository" from Tue?

-- 
Jakub Narebski
Poland

  parent reply	other threads:[~2008-11-09 11:51 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
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 [this message]
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=200811091249.40735.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=koreth@midwinter.com \
    --cc=mithro@mithis.com \
    --cc=pasky@suse.cz \
    --cc=peff@peff.net \
    --cc=spearce@spearce.org \
    /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).