From: Martin Langhoff <martin.langhoff@gmail.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: GIT <git@vger.kernel.org>
Subject: Re: git/cogito workshop/bof at linuxconf au?
Date: Sun, 14 Aug 2005 11:05:45 +1200 [thread overview]
Message-ID: <46a038f905081316056e83ebec@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0508131111270.19049@g5.osdl.org>
On 8/14/05, Linus Torvalds <torvalds@osdl.org> wrote:
> I was planning to be there. I like lca, but passed it over this year
> because of it being in Canberra
And how are things lining up for the upcoming one (January 2006, Dunedin, NZ)?
> > I would gladly try and organize a workshop, but I am far from fluent
> > with git, so I won't go at it alone. Any takers? Call for papers ends
> > 5th September, not too far ahead. We have to register our interest
> > _now_.
>
> I'm no good with papers, though.
Workshops and BOFs don't need to be paper-backed at all. Though it's
not unlikely that someone with an interest in SCM theory would write a
paper covering git. I think the main interest would be to bring git
practical usage to the masses.
There's a lot of interest, but the barriers of entry are somewhat
high, with the codebase moving fast, and some of the concepts
requiring re-learning of what to expect from an SCM. Perhaps no so
much among kernel hackers, but the general populace is largely still
laden with cvs/svn and their mindset.
cheers,
martin
next prev parent reply other threads:[~2005-08-13 23:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-13 7:34 git/cogito workshop/bof at linuxconf au? Martin Langhoff
2005-08-13 18:14 ` Linus Torvalds
2005-08-13 23:05 ` Martin Langhoff [this message]
2005-08-13 23:33 ` Linus Torvalds
2005-08-14 9:54 ` Petr Baudis
2005-08-15 19:17 ` Some tutorial text (was git/cogito workshop/bof at linuxconf au?) tony.luck
2005-08-15 22:44 ` Johannes Schindelin
2005-08-15 23:01 ` Some tutorial text 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=46a038f905081316056e83ebec@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).