From: Manuel Woelker <manuel.woelker@gmail.com>
To: git@vger.kernel.org
Subject: Git BoF @ EclipseCon
Date: Tue, 10 Mar 2009 09:10:40 +0100 [thread overview]
Message-ID: <3d045c7e0903100110i45fb1874s5e0dd3517e60695a@mail.gmail.com> (raw)
Hi git list!
Just a quick heads-up for all interested parties: There is a git BoF
scheduled for EclipseCon 2009 (
http://www.eclipsecon.org/2009/sessions?id=776 ). The main focus is
going to be to discuss how we can make git (probably via jgit/egit) a
viable option in the Eclipse ecosystem. A little more info here:
http://eclipsesource.com/blogs/2009/03/02/git-bof-eclipsecon/
I think it would be great to have some of you experts present there
and I hope we can make some progress. It also looks like there will be
another VCS BoF on Tuesday, to discuss more general issues
(IP, infrastructure, work flows, etc).
Cheers
- Manuel
next reply other threads:[~2009-03-10 8:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 8:10 Manuel Woelker [this message]
2009-03-10 14:25 ` Git BoF @ EclipseCon Shawn O. Pearce
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=3d045c7e0903100110i45fb1874s5e0dd3517e60695a@mail.gmail.com \
--to=manuel.woelker@gmail.com \
--cc=git@vger.kernel.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).