From: "Shawn O. Pearce" <spearce@spearce•org>
To: Jeff King <peff@peff•net>
Cc: Christian Couder <chriscool@tuxfamily•org>,
git@vger•kernel.org, Junio C Hamano <gitster@pobox•com>,
Scott Chacon <schacon@gmail•com>,
Sam Vilain <sam.vilain@catalyst•net.nz>,
Petr Baudis <pasky@suse•cz>
Subject: Re: GitTogether topics status (4th of October)
Date: Tue, 7 Oct 2008 07:46:43 -0700 [thread overview]
Message-ID: <20081007144643.GK8203@spearce.org> (raw)
In-Reply-To: <20081007031509.GA6031@coredump.intra.peff.net>
Jeff King <peff@peff•net> wrote:
> I just added two proposed half-hour meetings, both of which I intend to
> be a few minutes of me talking followed by group discussion. The topics
> are:
>
> 1. Helping new developers join the git community
Oh, this is a good idea. Yesterday I myself had trouble with
a new contributor not being familiar with the patching process.
Partly also my fault of still being a green maintainer. ;-)
> 2. What needs refactoring?
>
> I occasionally run up against parts of the code that just make my
> eyes bleed everytime I touch them. I think we've made significant
> progress in maintanability and bug-avoidance with things like the
> strbuf library, refactoring of remote and transport handling, etc.
> What areas might still benefit from such refactoring?
Also a good idea. I imagine Junio may have some interest in this.
I certainly do. Some of the code is just bloodly aweful to work
with. I guess those are the parts that make your eyes bleed.
--
Shawn.
next prev parent reply other threads:[~2008-10-07 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-04 16:16 GitTogether topics status (4th of October) Christian Couder
2008-10-07 3:15 ` Jeff King
2008-10-07 3:46 ` Nicolas Pitre
2008-10-07 14:38 ` Shawn O. Pearce
2008-10-07 14:46 ` Shawn O. Pearce [this message]
2008-10-17 19:18 ` René Scharfe
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=20081007144643.GK8203@spearce.org \
--to=spearce@spearce$(echo .)org \
--cc=chriscool@tuxfamily$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=pasky@suse$(echo .)cz \
--cc=peff@peff$(echo .)net \
--cc=sam.vilain@catalyst$(echo .)net.nz \
--cc=schacon@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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