From: Douglas Campos <douglas@theros.info>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Mark Struberg <struberg@yahoo.de>,
Jonas Fonseca <jonas.fonseca@gmail.com>,
Robin Rosenberg <robin.rosenberg.lists@dewire.com>,
git@vger.kernel.org, Jason van Zyl <jvanzyl@sonatype.com>
Subject: Re: [JGIT PATCH 1/9] mavenizing step 1: moved over the initial poms from Jasons branch Signed-off-by: Mark Struberg <struberg@yahoo.de>
Date: Wed, 30 Sep 2009 23:05:29 -0300 [thread overview]
Message-ID: <ed88cb980909301905u5e57f046kd7426e3090cf95c6@mail.gmail.com> (raw)
In-Reply-To: <20090930211646.GM14660@spearce.org>
> Worse, we now have to start following the Eclipse IP process[1]
> for submissions to JGit...
>
> [1] http://www.eclipse.org/projects/dev_process/ip-process-in-cartoons.php
>
How we'll handle this? Are the acks/signoffs that we use with mail
patches enough for this?
Painful process, BTW
--
Douglas Campos (qmx)
+55 11 7626 5959
prev parent reply other threads:[~2009-10-01 2:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 21:16 [JGIT PATCH 1/9] mavenizing step 1: moved over the initial poms from Jasons branch Signed-off-by: Mark Struberg <struberg@yahoo.de> Mark Struberg
[not found] ` <1253740570-10718-2-git-send-email-struberg@yahoo.de>
2009-09-23 21:16 ` [JGIT PATCH 3/9] moving some license files and META-INF Mark Struberg
2009-09-23 21:16 ` [JGIT PATCH 4/9] checkin all eclipse project file changes Mark Struberg
2009-09-23 21:16 ` [JGIT PATCH 5/9] mavenized org.spearce.jgit.pgm Mark Struberg
2009-09-23 21:16 ` [JGIT PATCH 6/9] enable missing test cases and fix jgit executable creation Mark Struberg
2009-09-23 21:16 ` [JGIT PATCH 7/9] removing eclipse project files Mark Struberg
2009-09-23 21:16 ` [JGIT PATCH 8/9] renamed the PathSuffixFilter test to JUnit conventions, so it gets executed via maven test Mark Struberg
2009-09-23 21:16 ` [JGIT PATCH 9/9] Add the <scm> section to the parent pom Mark Struberg
2009-09-24 6:29 ` [JGIT PATCH 7/9] removing eclipse project files Ferry Huberts
2009-09-24 6:55 ` Mark Struberg
2009-09-24 7:57 ` Ferry Huberts
2009-09-24 8:24 ` Mark Struberg
2009-09-24 8:57 ` Ferry Huberts
2009-09-24 8:57 ` Ferry Huberts
2009-09-25 21:40 ` Robin Rosenberg
2009-09-24 11:24 ` Sohn, Matthias
2009-09-24 11:50 ` Mark Struberg
2009-09-25 13:25 ` Douglas Campos
2009-09-25 21:17 ` Robin Rosenberg
2009-09-26 20:10 ` Mark Struberg
2009-09-27 19:52 ` Robin Rosenberg
2009-09-28 2:21 ` Jonas Fonseca
2009-09-28 6:34 ` Robin Rosenberg
2009-09-28 6:42 ` Robin Rosenberg
2009-09-25 21:33 ` [JGIT PATCH 1/9] mavenizing step 1: moved over the initial poms from Jasons branch Signed-off-by: Mark Struberg <struberg@yahoo.de> Robin Rosenberg
2009-09-26 19:50 ` Mark Struberg
2009-09-28 12:46 ` Jonas Fonseca
2009-09-30 19:51 ` Mark Struberg
2009-09-30 21:16 ` Shawn O. Pearce
2009-09-30 23:13 ` Mark Struberg
2009-09-30 23:16 ` Jason van Zyl
2009-10-01 11:15 ` Mark Struberg
2009-10-01 13:55 ` Jason van Zyl
2009-10-01 1:33 ` Jonas Fonseca
2009-10-01 2:05 ` Douglas Campos [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=ed88cb980909301905u5e57f046kd7426e3090cf95c6@mail.gmail.com \
--to=douglas@theros.info \
--cc=git@vger.kernel.org \
--cc=jonas.fonseca@gmail.com \
--cc=jvanzyl@sonatype.com \
--cc=robin.rosenberg.lists@dewire.com \
--cc=spearce@spearce.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).