git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg@dewire.com>
To: "Imran M Yousuf" <imyousuf@gmail.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
	git@vger.kernel.org, "Dave Watson" <dwatson@mimvista.com>,
	"Roger C. Soares" <rogersoares@intelinet.com.br>
Subject: Re: [jgit] index v2 pull request
Date: Mon, 10 Mar 2008 22:53:27 +0100	[thread overview]
Message-ID: <200803102253.28469.robin.rosenberg@dewire.com> (raw)
In-Reply-To: <7bfdc29a0803100032q6b30f16el97c021f3b051b944@mail.gmail.com>

Den Monday 10 March 2008 08.32.21 skrev Imran M Yousuf:
> I would like to volunteer to work in JGit;
> can someone let me know where I can pick some tasks to implement?
>

You can pick about anything you want that noone is working one. Pick something
that you feel is withing your grasp, or something simple outside. We need
more test cases (doesn't require much programming skills, but thinking). Unit
testing of Eclipse stuff falls into the same category. I have litte experience 
here, but I think there are lots of examples in Eclipse itself if one starts 
to poke around.

Diff against workspace/index doesn't work presently. The reworked 
indexdiffwalker or the iterator could be used for that. Please tell me if you 
start hacking on this as it's on my listl, just not yet. Should be reasonably 
hard, involves both jgit and eclipse programming.

There are some issues with selecting versions in the history view on Windows.

Copy diff as git patch to the clipboard and vice verse. Send email.

Harder and might involve more changes all over (that either I or Shawn will 
object to) is things like rename detection targeted fo r

Interface to quickdiff machinery for committing specific hunks.

Blame (even without rename detection) would be useful. Look at the CVS
annotate for inspiration. 

Support for git submodules. Will touch the core parts all over the place, but 
probably not in very intrusive way. Will require lots of test cases.

Not really git, but highlighting of trailing whitespace is on my wish list. I 
can't find a plugin that does that.

Adjust the commit dialog for amend so it shows all to-be commited changed 
files when amending.

The number of choices is infinite.

Ant, Cruisecontrol, Maven, etc-tasks.

Pick a pet.

-- robin

  reply	other threads:[~2008-03-11 14:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-08  2:50 [jgit] index v2 pull request Shawn O. Pearce
2008-03-08  9:08 ` Jakub Narebski
2008-03-09  0:51   ` Shawn O. Pearce
2008-03-09 23:51 ` Robin Rosenberg
2008-03-10  7:32   ` Imran M Yousuf
2008-03-10 21:53     ` Robin Rosenberg [this message]
2008-03-12  2:52       ` Imran M Yousuf
2008-03-12  7:07         ` Robin Rosenberg
2008-03-12  7:52           ` Shawn O. Pearce
2008-03-12  8:19           ` Imran M Yousuf
2008-03-11  0:35     ` Shawn O. Pearce
2008-03-11  2:24       ` Imran M Yousuf
2008-03-10 23:31   ` 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=200803102253.28469.robin.rosenberg@dewire.com \
    --to=robin.rosenberg@dewire.com \
    --cc=dwatson@mimvista.com \
    --cc=git@vger.kernel.org \
    --cc=imyousuf@gmail.com \
    --cc=rogersoares@intelinet.com.br \
    --cc=spearce@spearce.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).