git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Luis Ressel <aranea@aixah.de>
Cc: git <git@vger.kernel.org>
Subject: Re: [GSoC microproject] Add XDG support to the credential-store helper
Date: Thu, 5 Mar 2015 23:38:19 +0100	[thread overview]
Message-ID: <CAP8UFD3kHKsUWqmfr3mEtTYwVFwGGqMF_wJgVQyoaH=2i9Ge=A@mail.gmail.com> (raw)
In-Reply-To: <20150305215146.394caa71@gentp.lnet>

Hi,

On Thu, Mar 5, 2015 at 9:51 PM, Luis Ressel <aranea@aixah.de> wrote:
> I'm contributing this patch in preparation for a GSoC15 application with
> the git project. In particular, I'm interested in the two bisect
> improvements listed on the Ideas page. Does anyone have other
> suggestions for potential improvements of git bisect that would be
> suitable for such a GSoC project?

Last year, on the ideas page:

http://git.github.io/SoC-2014-Ideas.html

we also had the following improvement:

"in some cases, git bisect may test too many merge bases, thus slowing
down the bisection (making it closer to linear than logarithmic)."

so you could work on that too.

And if you really want and have time you can also rewrite
git-bisect.sh into a builtin command. There is already
builtin/bisect--helper.c where you can put some migrated code step by
step.

> Oh, and should I add a testcase for the new functionality introduced by
> this patch? And if yes, what exactly should I test?

First, it looks like another student started working on the same
microproject. Did you have a look at what he did? If you didn't, you
probably should, so that reviewers don't need to tell you what they
already told the other student. And if you did, you should tell it,
and maybe explain what you did differently and why.

If it looks like the other student is more advanced on this subject,
you might want to try another microproject. And if all the
microprojects are already taken, you might want to ask the list for
other microprojects, or you may want to have a look at the many merge
bases improvement above. (You could start by having a look at
check_merge_bases() in "bisect.c" and by creating a script or better a
test case that reproduces the problem, see
t/t6030-bisect-porcelain.sh.)

Welcome to the Git community!

Best,
Christian.

  parent reply	other threads:[~2015-03-05 22:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 20:51 [GSoC microproject] Add XDG support to the credential-store helper Luis Ressel
2015-03-05 20:53 ` [PATCH] " Luis Ressel
2015-03-05 22:10 ` [GSoC microproject] " Junio C Hamano
2015-03-05 22:38 ` Christian Couder [this message]
2015-03-05 23:15   ` Luis Ressel
2015-03-05 23:41     ` Luis Ressel
2015-03-06  8:04       ` Paul Tan
2015-03-06 17:28         ` Matthieu Moy
2015-03-06 19:21           ` Paul Tan

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAP8UFD3kHKsUWqmfr3mEtTYwVFwGGqMF_wJgVQyoaH=2i9Ge=A@mail.gmail.com' \
    --to=christian.couder@gmail.com \
    --cc=aranea@aixah.de \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).