From: "Shawn O. Pearce" <spearce@spearce.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [GSoC] Google Summer of Code 2009 - new ideas
Date: Mon, 9 Mar 2009 17:49:35 -0700 [thread overview]
Message-ID: <20090310004935.GM11989@spearce.org> (raw)
In-Reply-To: <200903070144.17457.jnareb@gmail.com>
Jakub Narebski <jnareb@gmail.com> wrote:
> I'd like to add a few ideas to SoC2009Ideas wiki page, but before I do
> this I'd like to ask for comments. (The proposals also lacks proposed
> mentor).
>
> I am wondering if it would be worth it to make a separate class between
> "New to Git?" easy tasks, and "Larger Projects" hard tasks...
Done, there is now a "Medium" category. Folks should start to
repaint the bikeshed if they disagre with my current choices
in colors.
> BTW. some of ideas didn't make it from SoC2008Ideas wiki page to current
> year page, namely:
> * Apply sparse To Fix Errors
> * Lazy clone / remote alternates
> * Implement git-submodule using .gitlink file
> * Teach git-apply the 3-way merge fallback git-am knows
> * Better Emacs integration
> Was this ommision deliberate or accidental?
Accidental. Most have been added back. Of note I did not add back
the emacs integration as we have multiple emacs packages.
--
Shawn.
prev parent reply other threads:[~2009-03-10 0:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 0:44 [GSoC] Google Summer of Code 2009 - new ideas Jakub Narebski
2009-03-07 1:09 ` Jan Janak
2009-03-07 2:56 ` Tay Ray Chuan
2009-03-08 23:59 ` Jakub Narebski
[not found] ` <20090309115026.obsvt34miowwcw8w@webmail.fussycoder.id.au>
2009-03-09 1:18 ` Jakub Narebski
2009-03-07 19:59 ` P Baker
2009-03-07 20:55 ` Shawn O. Pearce
2009-03-10 0:49 ` Shawn O. Pearce [this message]
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=20090310004935.GM11989@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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.