From: Petr Baudis <pasky@suse.cz>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Junio C Hamano <gitster@pobox.com>,
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 18:06:10 +0200 [thread overview]
Message-ID: <20080822160609.GO10544@machine.or.cz> (raw)
In-Reply-To: <20080822160008.GN10544@machine.or.cz>
On Fri, Aug 22, 2008 at 06:00:08PM +0200, Petr Baudis wrote:
> On Fri, Aug 22, 2008 at 07:34:07AM -0700, Shawn O. Pearce wrote:
> > 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.
>
> Also, if this event would indeed be in US, some of the developers would
> need to arrange visa, which takes time too (though the time can vary,
> reportedly - but 30 days should be enough).
(Then again, after a moment of thought, I'm not sure about the actual
scale of the event - if it's just a short thing for a day or two, a trip
from Europe probably does not make much sense. But if we could think up
enough for four days of fun, it would be probably worth it.)
Didn't Johannes mention that he will be in US in October?
--
Petr "Pasky" Baudis
The next generation of interesting software will be done
on the Macintosh, not the IBM PC. -- Bill Gates
next prev parent reply other threads:[~2008-08-22 16:07 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 [this message]
2008-08-22 16:14 ` Shawn O. Pearce
2008-08-22 18:58 ` Andreas Ericsson
2008-08-22 21:17 ` Junio C Hamano
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=20080822160609.GO10544@machine.or.cz \
--to=pasky@suse.cz \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=chriscool@tuxfamily.org \
--cc=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.