git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Christian Couder <chriscool@tuxfamily.org>,
	"J.H." <warthog19@eaglescrag.net>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Daniel Barkalow <barkalow@iabervon.org>,
	Sam Vilain <sam.vilain@catalyst.net.nz>,
	David Symonds <dsymonds@gmail.com>,
	git@vger.kernel.org
Subject: Re: Gittogether event?
Date: Fri, 22 Aug 2008 14:17:58 -0700	[thread overview]
Message-ID: <7vzln47nqx.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 20080822143407.GE3483@spearce.org

"Shawn O. Pearce" <spearce@spearce.org> writes:

> Junio C Hamano <gitster@pobox.com> wrote:
> ...
>> If Git-together happens outside of that, I could join.
>
> I think it would be after that.  I doubt we could put it together
> with <30 days of notice.  Most people who would want to attend need
> to book travel arrangements.  While its possible with 30 days notice
> you can typically get better rates if you have more lead time.

Ah, I somehow got a wrong impression about this event from the initial
posting, and certainly didn't imagine you were planning a mini-conference
like one, but a much more informal and smaller "while some of us are in
the west coast during/near GSoC mentor thing, how about getting together
for fun" kind of settings.

It all makes sense now.

  parent reply	other threads:[~2008-08-22 21:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080820151031.GD3483@spearce.org>
     [not found] ` <200808210432.10544.chriscool@tuxfamily.org>
     [not found]   ` <20080821144537.GM3483@spearce.org>
2008-08-22  3:36     ` Gittogether event? (was: GSoC 2008 final evaluations) Christian Couder
2008-08-22  6:27       ` Gittogether event? Junio C Hamano
2008-08-22 14:34         ` Shawn O. Pearce
     [not found]           ` <32541b130808220739x632d1590v7894b7dfe94c4de@mail.gmail.com>
2008-08-22 14:44             ` Shawn O. Pearce
2008-08-22 16:00           ` Petr Baudis
2008-08-22 16:06             ` Petr Baudis
2008-08-22 16:14               ` Shawn O. Pearce
2008-08-22 18:58             ` Andreas Ericsson
2008-08-22 21:17           ` Junio C Hamano [this message]
2008-08-23  0:31             ` Shawn O. Pearce
2008-08-23  5:26               ` Christian Couder
2008-08-23  5:25                 ` J.H.
2008-08-23 19:42                 ` Shawn O. Pearce
2008-08-23  6:23           ` Junio C Hamano
2008-08-25 19:15           ` Christian Couder
2008-08-25 19:23             ` Shawn O. Pearce
2008-08-25 20:38               ` Johannes Schindelin
2008-08-25 21:11                 ` Christian Couder
2008-08-26  4:30           ` Sam Vilain
2008-08-26 20:48             ` Christian Couder
2008-08-26 20:59               ` Daniel Barkalow
2008-08-27 23:45               ` Sam Vilain
2008-08-28  4:07                 ` Christian Couder
2008-08-23  2:50       ` Gittogether event? (was: GSoC 2008 final evaluations) Greg KH
2008-08-23  5:06         ` Christian Couder

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=7vzln47nqx.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=barkalow@iabervon.org \
    --cc=chriscool@tuxfamily.org \
    --cc=dsymonds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sam.vilain@catalyst.net.nz \
    --cc=spearce@spearce.org \
    --cc=warthog19@eaglescrag.net \
    /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).