From: Jonas Fonseca <jonas.fonseca@gmail.com>
To: Mark Struberg <struberg@yahoo.de>
Cc: Douglas Campos <douglas@theros.info>,
git@vger.kernel.org, Gabe McArthur <gabriel.mcarthur@gmail.com>
Subject: Re: [JGIT] Request for help
Date: Fri, 4 Sep 2009 14:50:58 -0400 [thread overview]
Message-ID: <2c6b72b30909041150g6374be2ci4d36bd8ab0824a8d@mail.gmail.com> (raw)
In-Reply-To: <658028.86274.qm@web27804.mail.ukl.yahoo.com>
On Fri, Sep 4, 2009 at 13:28, Mark Struberg<struberg@yahoo.de> wrote:
> Hi!
>
> Work has been done at
>
> http://github.com/sonatype/JGit/tree/mavenize
>
> Please feel free to pull/fork and share your changes! I'd be happy to pull it in.
IMO, there are a lot of things that can be squashed together and
cleaned up. I know that you advocated for incremental introduction,
but it seems wrong to for example add a file and then completely
reformat it a few commits later. The same thing with the .gitignore
fixes in step 5.
Some comments ... Some of them I initially entered in github's
codereview, but I ended up writing it all here.
Commit: "mavenizing step 1: moved over the initial poms from Jasons branch"
* Please always add an empty line between the subject and the body
of the commit message. Like this:
mavenizing step 1: moved over the initial poms from Jasons branch
Signed-off-by: Mark Struberg >struberg@yahoo.de>
* The .gitignore pattern could be further limited to "target/" ...
but you seem to change this to /target later.
In org.spearce.jgit/pom.xml:
* The use of maven-surefire-plugin should be removed. This module
does not have any tests.
* Shouldn't we retain the original ${groupId}:${artifactId} naming
convention, being org.spearce:jgit?
In org.spearce.jgit.test/pom.xml:
* Dependency on jsch is unecessary since it is derived from
org.spearce.jgit.
* Maybe name as org.spearce:jgit-test?
In org.spearce.jgit.pgm/pom.xml:
* Maybe name as org.spearce:jgit-pgm?
Commit: "mavenizing step 2: move the core libs from src to src/main/java"
* Please also add an empty line to this commit message.
* You might as well squash the whitespace fixes into the first commit.
Commit: "mavenizing step 3: moving all core tests into the core module"
* The commit message wrongly states:
org.spearce.jgit.test/tst/ -> org.spearce.jgit/src/test/java/tst/
Should be:
org.spearce.jgit.test/tst/ -> org.spearce.jgit/src/test/java/
Commit: "mavenizing step 4: moving some license files and META-INF"
* Shouldn't the commit message rather say "remove JSch"?
Then the moving of META-INF can be put in its own commit.
* The new NOTICE file has a few typos and the info could fit into the README
Then I got a bit lost in a huge reformatting.
--
Jonas Fonseca
next prev parent reply other threads:[~2009-09-04 18:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ed88cb980909040744k2fa372fapb7ee457c745b9aa0@mail.gmail.com>
2009-09-04 14:49 ` [JGIT] Request for help Mark Struberg
2009-09-04 17:28 ` Mark Struberg
2009-09-04 18:50 ` Jonas Fonseca [this message]
2009-09-04 18:54 ` Mark Struberg
2009-09-04 19:51 ` Mark Struberg
2009-09-04 23:47 ` Gabe
2009-09-05 0:06 ` Douglas Campos
2009-09-05 1:29 ` Gabe McArthur
2009-09-05 16:25 ` Robin Rosenberg
2009-09-05 16:40 ` Mark Struberg
2009-09-04 7:12 Mark Struberg
-- strict thread matches above, loose matches on Subject: below --
2009-09-02 23:28 Nasser Grainawi
2009-09-03 0:04 ` Johannes Schindelin
2009-09-03 1:22 ` Shawn O. Pearce
2009-09-03 12:45 ` Jonas Fonseca
2009-09-03 14:42 ` Shawn O. Pearce
2009-09-03 15:38 ` Jonas Fonseca
2009-09-03 15:52 ` Shawn O. Pearce
2009-09-04 5:00 ` Gabe McArthur
2009-09-04 7:33 ` Mark Struberg
2009-09-04 12:22 ` Jonas Fonseca
2009-09-04 12:27 ` Mark Struberg
2009-09-04 12:41 ` Jonas Fonseca
2009-09-04 12:47 ` Mark Struberg
2009-09-03 1:23 ` Shawn O. Pearce
2009-09-03 19:46 ` Nasser Grainawi
2009-09-03 19:49 ` Shawn O. Pearce
2009-09-03 21:09 ` Nasser Grainawi
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=2c6b72b30909041150g6374be2ci4d36bd8ab0824a8d@mail.gmail.com \
--to=jonas.fonseca@gmail.com \
--cc=douglas@theros.info \
--cc=gabriel.mcarthur@gmail.com \
--cc=git@vger.kernel.org \
--cc=struberg@yahoo.de \
/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).