tomaswolf closed pull request #430: GH-429: Support GIT protocol-v2
URL: https://github.com/apache/mina-sshd/pull/430
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment
tomaswolf closed issue #429: Support GIT protocol-v2
URL: https://github.com/apache/mina-sshd/issues/429
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail
lgoldstein commented on issue #429:
URL: https://github.com/apache/mina-sshd/issues/429#issuecomment-1850540081
Merged as
[43288b58c7](https://github.com/apache/mina-sshd/commit/f5c63a87d46ca5820e17af00b4e65a43288b58c7)
--
This is an automated message from the Apache Git Service
the PR
now.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For queries about this service, please contact Infrastructure
lgoldstein commented on code in PR #430:
URL: https://github.com/apache/mina-sshd/pull/430#discussion_r1418394044
##
sshd-git/src/main/java/org/apache/sshd/git/transport/GitSshdSession.java:
##
@@ -133,7 +132,16 @@ public Process exec(String commandName, int timeout)
throws
mantics we treat them as "equivalent" to *null*. See my 2
comments - once you fix this I would be happy to merge this in. Good job on the
whole...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above t
pflaska commented on code in PR #430:
URL: https://github.com/apache/mina-sshd/pull/430#discussion_r1416286714
##
sshd-git/src/main/java/org/apache/sshd/git/pack/GitPackCommand.java:
##
@@ -77,7 +79,11 @@ public void run() {
Repository db = key.open(true /* must
pflaska commented on code in PR #430:
URL: https://github.com/apache/mina-sshd/pull/430#discussion_r1416276242
##
sshd-git/src/main/java/org/apache/sshd/git/transport/GitSshdSession.java:
##
@@ -30,13 +32,16 @@
import org.eclipse.jgit.transport.CredentialsProvider;
import
lgoldstein commented on code in PR #430:
URL: https://github.com/apache/mina-sshd/pull/430#discussion_r1381259350
##
sshd-git/src/main/java/org/apache/sshd/git/pack/GitPackCommand.java:
##
@@ -77,7 +79,11 @@ public void run() {
Repository db = key.open(true /* must
lgoldstein commented on code in PR #430:
URL: https://github.com/apache/mina-sshd/pull/430#discussion_r1381259350
##
sshd-git/src/main/java/org/apache/sshd/git/pack/GitPackCommand.java:
##
@@ -77,7 +79,11 @@ public void run() {
Repository db = key.open(true /* must
github.com/apache/mina-sshd/issues/429
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For queries about this service, plea
pflaska opened a new issue, #429:
URL: https://github.com/apache/mina-sshd/issues/429
### Description
To make the git protocol-v2 work, the env. variable GIT_PROTOCOL has to be
set to the 'version=2' value on the client side. The SSHD server reads the
variable and sets extra
since it's not Git specific. It would eliminate the dependency for sshd-git
jar. If not, I will think of copying and renaming {{GitSshdSessionProcess}}.
{quote}
Btw, you're saying you're migrating from Jsch but afaik, it does not provide
this kind of abstraction (for the same reason I suppose
}} in the same way as SSHD ...
> is GitSshdSessionProcess class Git specific?
> -
>
> Key: SSHD-1243
> URL: https://issues.apache.org/jira/browse/SSHD-1243
> Project: MINA SSHD
>
something
like {{SSHDProcess}} extending {{java.lang.Process}}.
If i am not wrong, {{GitSshdSessionProcess}} is not inluded in ssh-core and
sshd-common jar files. It is included sshd-git jar.
Do you have a plan a renamed class like {{SSHDProcess}} in more generic
ssd-core, sshd-common, etc. jar files
[
https://issues.apache.org/jira/browse/SSHD-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed SSHD-1243.
-
Assignee: Guillaume Nodet
Resolution: Not A Problem
> is GitSshdSessionProcess class
[
https://issues.apache.org/jira/browse/SSHD-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17484225#comment-17484225
]
Guillaume Nodet commented on SSHD-1243:
---
It's not really git specific but definitely SSHD specific
dgü created SSHD-1243:
-
Summary: is GitSshdSessionProcess class Git specific?
Key: SSHD-1243
URL: https://issues.apache.org/jira/browse/SSHD-1243
Project: MINA SSHD
Issue Type: Question
Affects
Hi Emmanuel,
Things are definitely moving smoothly; I can say the migration already has been
completed and
mina.a.o is served from git now.
One thing that may be good to do is add a MOVED_TO_GIT here [1]. MINA has
already been
disabled from the CMS. Also, the Jenkins job [2] seems to do its
Hi Roy,
are things moving smoothly ? When do you think we would be able to done
? (just wondering, no urgence).
Thanks a lot !
-
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail:
Thanks Guillaume! The Jenkins job for building the site has been created [1],
and a PR for moving
over is created as well [2]
Last chance to say goodbye to the CMS :P
[1] https://builds.apache.org/job/mina-site/
[2] https://github.com/apache/infrastructure-puppet/pull/1730
On 2020/02/24
I've pushed the 4 branches.
Thx !
Le lun. 24 févr. 2020 à 16:41, Roy Lenferink a
écrit :
> Thanks Emmanuel! Requesting repositories is selfservice, so indeed they
> will be available pretty
> quick :)
>
> I have everything available in my copy of the mina-site repository here
> [1]
>
> The
Hey Emanuell,
I missed the vote… but I am +1 too…
Jeff
> On Feb 24, 2020, at 8:41 AM, Roy Lenferink wrote:
>
> Thanks Emmanuel! Requesting repositories is selfservice, so indeed they will
> be available pretty
> quick :)
>
> I have everything available in my copy of the mina-site
Thanks Emmanuel! Requesting repositories is selfservice, so indeed they will be
available pretty
quick :)
I have everything available in my copy of the mina-site repository here [1]
The repository contains the 4 needed branches:
- asf-site => contains the generated content which will be
On 24/02/2020 09:38, Emmanuel Lécharny wrote:
Hi,
On 22/02/2020 16:21, Roy Lenferink wrote:
Hi,
The vote has passed with the following results:
+1 Guillaume Nodet (binding)
+1 Emmanuel Lécharny (binding)
+1 Jeff Maury (binding)
+1 Roy Lenferink (non-binding)
No -1 votes have been cast.
Hi,
On 22/02/2020 16:21, Roy Lenferink wrote:
Hi,
The vote has passed with the following results:
+1 Guillaume Nodet (binding)
+1 Emmanuel Lécharny (binding)
+1 Jeff Maury (binding)
+1 Roy Lenferink (non-binding)
No -1 votes have been cast.
To continue I'll need some help from a PMC member
out with
this so let me know when someone is available).
After having the site in place, I'll create a Jenkins job, test whether it
works and open a pull request
against the infrastructure-puppet repository to make the actual switch from svn
to git.
Best,
Roy
[1] https://gitbox.apache.org/setup
Adding my +1 (non-binding) as well.
On 2020/02/19 13:45:51, Roy Lenferink wrote:
> Hi MINA community,
>
> After last weeks proposal [1] I'd like to start a formal vote for moving over
> from the current Apache
> CMS (and SVN) to use Hugo and git.
>
> Short recap about H
> > écrit :
> >
> >> Hi MINA community,
> >>
> >> After last weeks proposal [1] I'd like to start a formal vote for moving
> >> over from the current Apache
> >> CMS (and SVN) to use Hugo and git.
> >>
> >> Short recap about Hugo: Hug
(and SVN) to use Hugo and git.
Short recap about Hugo: Hugo is a static site generator which is already
having more stars on
GitHub than Jekyll. It is easy to get started with (single static binary
without dependencies) and it is
really doing well performance wise.
[ ] +1 for moving over from
+1
Thx for pushing that. The change will be a huge gain.
Le mer. 19 févr. 2020 à 14:45, Roy Lenferink a
écrit :
> Hi MINA community,
>
> After last weeks proposal [1] I'd like to start a formal vote for moving
> over from the current Apache
> CMS (and SVN) to use Hugo and git.
Apologies if I missed something!
This is about moving the source for the mina.apache.org site, which is
currently served from SVN [1],
to a new mina-site git repository (to be created after vote passes). This
repository will be synced
between gitbox.a.o and GitHub. After this, I will create
Just to clarify - is this about moving to Git on GitHub, or is it
about moving to Git using a different host for the upstream
repository?
On Wed, Feb 19, 2020 at 7:52 AM Roy Lenferink wrote:
>
> Hi MINA community,
>
> After last weeks proposal [1] I'd like to start a formal vote for
Hi MINA community,
After last weeks proposal [1] I'd like to start a formal vote for moving over
from the current Apache
CMS (and SVN) to use Hugo and git.
Short recap about Hugo: Hugo is a static site generator which is already having
more stars on
GitHub than Jekyll. It is easy to get
rote:
> > > > Hello MINA developers,
> > > >
> > > > I noticed MINA is still serving its site from SVN with help of the
> > > > Apache
> > > > CMS.
> > >
> > > Yes. It has been this way for around a decade (actual
rator.
> >
> >
> > > At the Apache Celix project we decided to move away from the CMS and move
> > > towards git for serving our website [1]. The master branch contains the
> > > actual
> > > website sources whereas the generated website is serv
he Apache
> > CMS.
>
> Yes. It has been this way for around a decade (actually, as soon as the
> CMS was proposed). before that we were using a buggy Confluence ->
> website generator.
>
>
> > At the Apache Celix project we decided to move away from the CMS and
->
website generator.
At the Apache Celix project we decided to move away from the CMS and move
towards git for serving our website [1]. The master branch contains the
actual
website sources whereas the generated website is served from the asf-site
branch.
Hugo is being used as static webs
Hello MINA developers,
I noticed MINA is still serving its site from SVN with help of the Apache
CMS.
At the Apache Celix project we decided to move away from the CMS and move
towards git for serving our website [1]. The master branch contains the
actual
website sources whereas the generated
On 20/05/2019 18:17, Jonathan Valliere wrote:
Oh, two mirrors. How do we remove the bad one?
I guess we should ask infra...
Oh, two mirrors. How do we remove the bad one?
On Mon, May 20, 2019 at 12:16 PM Emmanuel Lécharny
wrote:
>
> On 20/05/2019 18:02, Jonathan Valliere wrote:
> > The GitHub Mirror of FTPSERVER is not automatically updating from Gitbox.
> > How do we fix this?
>
>
> I think it does, but there are
On 20/05/2019 18:02, Jonathan Valliere wrote:
The GitHub Mirror of FTPSERVER is not automatically updating from Gitbox.
How do we fix this?
I think it does, but there are 2 mirrors, one being ftpserver and has
stalled, and the other one being mina-ftpserver and seems to be
up-to-date with
The GitHub Mirror of FTPSERVER is not automatically updating from Gitbox.
How do we fix this?
Thanks for the headsup !
All the site has been updated.
On 06/02/2019 00:19, Jonathan Valliere wrote:
We need to update all the website pages to point to gitbox. All of the
projects continue to list git-wip-us.apache.org
On Sat, Jan 12, 2019 at 6:10 AM Lyor Goldstein
wrote
We need to update all the website pages to point to gitbox. All of the
projects continue to list git-wip-us.apache.org
On Sat, Jan 12, 2019 at 6:10 AM Lyor Goldstein
wrote:
> >> The repositories have been migrated.
> >> Please update the main pom to point to the new locations.
>
> Done.
>
>> The repositories have been migrated.
>> Please update the main pom to point to the new locations.
Done.
The repositories have been migrated.
Please update the main pom to point to the new locations.
Le sam. 12 janv. 2019 à 10:27, Guillaume Nodet a écrit :
> I've updated the jira issue to point to this thread, asking to migrate all
> our repositories:
>
I've updated the jira issue to point to this thread, asking to migrate all
our repositories:
https://issues.apache.org/jira/browse/INFRA-17374
Cheers,
Guillaume
Le jeu. 3 janv. 2019 à 19:48, Guillaume Nodet a écrit :
> Rename for broader subject to affect all repositories.
>
> Le jeu. 3
Rename for broader subject to affect all repositories.
Le jeu. 3 janv. 2019 à 19:05, Lyor Goldstein a
écrit :
> >> +1 for me Unless someone objects, I think we should move all mina
> repositories.
>
> +1 for me as well
>
> How do we got about to provide the required "proof" that the vote has
>> +1 for me Unless someone objects, I think we should move all mina
repositories.
+1 for me as well
How do we got about to provide the required "proof" that the vote has been
taken ? Who else needs to vote and how do we record it in the JIRA issue ?
I am going to be unavailable for the next 3
Right, sorry I missed that thread, thx !
Le jeu. 3 janv. 2019 à 17:29, Lyor Goldstein a
écrit :
> >> Unless someone has any problem with the migration, I'm going to create
> the JIRA early next week to comply.
>
> No problem from my end - but I already opened
>
e link
> to the discussion on this issue so I am asking you to vote on it so we can
> go ahead and do it.
>
> Thanks.
> Lyor
>
> Daniel Gruno
> Fri 12/7/2018, 6:53 PM
> us...@infra.apache.org
>
> [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
>
>> Unless someone has any problem with the migration, I'm going to create
the JIRA early next week to comply.
No problem from my end - but I already opened
https://issues.apache.org/jira/browse/INFRA-17374 - all that is required is
a recorded vote (which I also sent an e-mail on this list).
Unless someone has any problem with the migration, I'm going to create the
JIRA early next week to comply.
Guillaume
Le jeu. 3 janv. 2019 à 14:19, Apache Infrastructure Team <
infrastruct...@apache.org> a écrit :
> Hello, mina folks.
> As stated earlier in 2018, all git repos
Hello, mina folks.
As stated earlier in 2018, all git repositories must be migrated from
the git-wip-us.apache.org URL to gitbox.apache.org, as the old service
is being decommissioned. Your project is receiving this email because
you still have repositories on git-wip-us that needs to be migrated
>> Do we have to do this for MINA also?
I believe so - see the original mail I posted. Anyway, seems it is not up
to us - anyone not initiating such a migration will be migrated anyway. I
have sent this mail since they require a documented discussion/vote if one
initiates the transition before
sking you to vote on it so we can
> go ahead and do it.
>
> Thanks.
> Lyor
>
> Daniel Gruno
> Fri 12/7/2018, 6:53 PM
> us...@infra.apache.org
>
> [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
> DISREGARD THIS EMAIL; IT WAS MASS-MAILE
...@infra.apache.org
[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]
Hello Apache projects,
I am writing to you because you may have git repositories on the
git-wip-us server, which is slated
...@infra.apache.org
[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]
Hello Apache projects,
I am writing to you because you may have git repositories on the
git-wip-us server, which is slated
[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]
Hello Apache projects,
I am writing to you because you may have git repositories on the
git-wip-us server, which is slated to be decommissioned in the coming
:48 GMT+02:00 <lgoldst...@apache.org>:
> [SSHD-819] Standardized the DelegateCommandFactory behavior
>
>
> Project: http://git-wip-us.apache.org/repos/asf/mina-sshd/repo
> Commit: http://git-wip-us.apache.org/repos/asf/mina-sshd/commit/f1a8077b
> Tree: http://git-wip-us.apache
> +public static byte[] readOakleyGroup(String name) {
>
The method was private, but making it public would need just a bit of
javadoc explaining the input/output.
I don't really see the need, since we have the getP16() and similar methods
that are already public though...
>> In general in
gt; Could you add the needed repository please ?
>>>>
>>>> 2017-03-02 21:00 GMT+01:00 <lgoldst...@apache.org>:
>>>>
>>>>> Repository: mina-sshd
>>>>> Updated Branches:
>>>>> refs/heads/master 8e255459a -> c
ldst...@apache.org>:
>>
>>> Repository: mina-sshd
>>> Updated Branches:
>>> refs/heads/master 8e255459a -> cbb92d2a8
>>>
>>>
>>> [SSHD-727] Upgrade used EdDSA artifact version to 1.1
>>>
>>>
>>> Project: h
DSA artifact version to 1.1
>
>
> Project: http://git-wip-us.apache.org/repos/asf/mina-sshd/repo
> Commit: http://git-wip-us.apache.org/repos/asf/mina-sshd/commit/cbb92d2a
> Tree: http://git-wip-us.apache.org/repos/asf/mina-sshd/tree/cbb92d2a
> Diff: http://git-wip-us.apache.org/repos
Receive does not anymore close the session (it's already
> closed on the client)
> - looping 10 000 times
> - removing the verbose logs, adding some logs and a counter.
>
> Project: http://git-wip-us.apache.org/repos/asf/mina/repo
> Commit: http://git-wip-us.apache.org/repos/asf/mina/comm
tch to git for the release process
>
>
> Key: DIRMINA-986
> URL: https://issues.apache.org/jira/browse/DIRMINA-986
> Project: MINA
> Issue Type: Task
ite to reflect the switch to git for the release process
>
>
> Key: DIRMINA-986
> URL: https://issues.apache.org/jira/browse/DIRMINA-986
> Project: MINA
>
ite to reflect the switch to git for the release process
>
>
> Key: DIRMINA-986
> URL: https://issues.apache.org/jira/browse/DIRMINA-986
> Project: MINA
>
ite to reflect the switch to git for the release process
>
>
> Key: DIRMINA-986
> URL: https://issues.apache.org/jira/browse/DIRMINA-986
> Project: MINA
>
ite to reflect the switch to git for the release process
>
>
> Key: DIRMINA-986
> URL: https://issues.apache.org/jira/browse/DIRMINA-986
> Project: MINA
>
ite to reflect the switch to git for the release process
>
>
> Key: DIRMINA-986
> URL: https://issues.apache.org/jira/browse/DIRMINA-986
> Project: MINA
> Issue Ty
Le 22/12/14 11:39, Jeff MAURY a écrit :
+1 for 2 interfaces
Ok, now that's complicated...
Now that 2.0.9 is out, we have many users that have already change their
code to fit with the broken interface.
If we rollback this change, we will break again the API, and we will
upset tehm once more.
[maven-release-plugin] prepare for next development iteration
Project: http://git-wip-us.apache.org/repos/asf/mina/repo
Commit: http://git-wip-us.apache.org/repos/asf/mina/commit/4bb91e3d
Tree: http://git-wip-us.apache.org/repos/asf/mina/tree/4bb91e3d
Diff: http://git-wip-us.apache.org/repos/asf
Le 22/12/14 10:28, Jeff MAURY a écrit :
Given the fact that we introduced some kind of incompatibility (with 2.0.9
or 2.0.10), don't you think it would be valuable to witch to 2.1.X ?
We probably should. My mistake would then be fixed.
Le 22/12/14 11:05, Emmanuel Lécharny a écrit :
Le 22/12/14 10:28, Jeff MAURY a écrit :
Given the fact that we introduced some kind of incompatibility (with 2.0.9
or 2.0.10), don't you think it would be valuable to witch to 2.1.X ?
We probably should. My mistake would then be fixed.
The real
Le 22/12/14 11:26, Emmanuel Lécharny a écrit :
Le 22/12/14 11:05, Emmanuel Lécharny a écrit :
Le 22/12/14 10:28, Jeff MAURY a écrit :
Given the fact that we introduced some kind of incompatibility (with 2.0.9
or 2.0.10), don't you think it would be valuable to witch to 2.1.X ?
We probably
+1 for 2 interfaces
Jeff
On Mon, Dec 22, 2014 at 11:36 AM, Emmanuel Lécharny elecha...@gmail.com
wrote:
Le 22/12/14 11:26, Emmanuel Lécharny a écrit :
Le 22/12/14 11:05, Emmanuel Lécharny a écrit :
Le 22/12/14 10:28, Jeff MAURY a écrit :
Given the fact that we introduced some kind of
Le 22/12/14 11:39, Jeff MAURY a écrit :
+1 for 2 interfaces
Ok, I'll do that.
Jeff, can you delete the tag I just created for MINA 2.0.10 ?
Thanks !
Done
Jeff
On Mon, Dec 22, 2014 at 11:57 AM, Emmanuel Lécharny elecha...@gmail.com
wrote:
Le 22/12/14 11:39, Jeff MAURY a écrit :
+1 for 2 interfaces
Ok, I'll do that.
Jeff, can you delete the tag I just created for MINA 2.0.10 ?
Thanks !
--
Jeff MAURY
Legacy code often differs
Hello,
I noticed Mina Jenkins jobs randomly failed when performing the git tag
command.
I opened a JIRA on INFRA (https://issues.apache.org/jira/browse/BUILDS-20).
But does anyone of you knows why the tag option has been set for the MINA
jobs ?
I removed it for the MINA2 Windows job but should
Emmanuel Lecharny created DIRMINA-986:
-
Summary: Update the web site to reflect the switch to git for the
release process
Key: DIRMINA-986
URL: https://issues.apache.org/jira/browse/DIRMINA-986
[
https://issues.apache.org/jira/browse/SSHD-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved SSHD-241.
--
Resolution: Fixed
Fix Version/s: 0.12.0
https://git-wip-us.apache.org/repos/asf?p=mina
Hi Guillaume,
any reason not to use the mina-core class instead of copying it in sshd ?
Le 12/3/13 3:43 PM, gno...@apache.org a écrit :
Updated Branches:
refs/heads/master 9a27e7284 - 11415ce63
[SSHD-259] Provide Base64 in sshd
Project: http://git-wip-us.apache.org/repos/asf/mina-sshd
Le 12/3/13 4:29 PM, Emmanuel Lécharny a écrit :
Hi Guillaume,
any reason not to use the mina-core class instead of copying it in sshd ?
Sorry, just read SSHD-259. So it makes sense...
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Question : are we requiring Java 7 for MINA 3 ?
Wondering because this code will not build on Java 6 :
Le 10/28/13 4:55 PM, jvermill...@apache.org a écrit :
Updated Branches:
refs/heads/trunk e2e0ac8ff - 2ff729a63
@@ -52,7 +52,13 @@ public class NioSelectorLoop implements SelectorLoop {
We stated for java 7 only a few month ago.
--
Julien Vermillard http://people.apache.org/~jvermillard/
On Mon, Oct 28, 2013 at 5:13 PM, Emmanuel Lécharny elecha...@gmail.com wrote:
Question : are we requiring Java 7 for MINA 3 ?
Wondering because this code will not build on Java 6 :
Le
Le 10/28/13 6:06 PM, Julien Vermillard a écrit :
We stated for java 7 only a few month ago.
My bad...
Sorry for the noise.
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
There is still one line of commented code in CoapDecoder
Jeff
—
Sent from Mailbox for iPhone
On Thu, Jul 25, 2013 at 3:00 PM, null apali...@apache.org wrote:
Updated Branches:
refs/heads/trunk 51dd5213d - 52009f32f
fixed sonar violations
Project: http://git-wip-us.apache.org/repos/asf
in CoapDecoder
Jeff
—
Sent from Mailbox for iPhone
On Thu, Jul 25, 2013 at 3:00 PM, null apali...@apache.org wrote:
Updated Branches:
refs/heads/trunk 51dd5213d - 52009f32f
fixed sonar violations
Project: http://git-wip-us.apache.org/repos/asf/mina/repo
Commit: http://git-wip
line of commented code in CoapDecoder
Jeff
—
Sent from Mailbox for iPhone
On Thu, Jul 25, 2013 at 3:00 PM, null apali...@apache.org wrote:
Updated Branches:
refs/heads/trunk 51dd5213d - 52009f32f
fixed sonar violations
Project: http://git-wip-us.apache.org/repos/asf/mina/repo
Project: http://git-wip-us.apache.org/repos/asf/mina/repo
Commit: http://git-wip-us.apache.org/repos/asf/mina/commit/52009f32
Tree: http://git-wip-us.apache.org/repos/asf/mina/tree/52009f32
Diff: http://git-wip-us.apache.org/repos/asf/mina/diff/52009f32
Branch: refs/heads/trunk
Commit
[
https://issues.apache.org/jira/browse/SSHD-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed SSHD-201.
Resolution: Won't Fix
Can't reproduce with safari 6.0.5
Using git over sshd
, please ignore it.
It seems to me that this issue is caused by invoking git in the windows
environment.
One thing that may work better would be to use a custom ProcessShellFactory
which would start a cygwin env and call git from there I suppose.
Another possibility would be to have the shell
[
https://issues.apache.org/jira/browse/SSHD-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on SSHD-241 started by Guillaume Nodet.
Git/SSH command support
---
Key: SSHD-241
URL: https
Guillaume Nodet created SSHD-241:
Summary: Git/SSH command support
Key: SSHD-241
URL: https://issues.apache.org/jira/browse/SSHD-241
Project: MINA SSHD
Issue Type: New Feature
.
This module contains an SSHD CommandFactory to support git through SSH.
The git commands are provided by a modified version of jgit-pgm
available at:
https://github.com/gnodet/jgit/tree/%23413522
Once the fixes in that branch have been included and released, we'll be able to
include
PM, sebb a écrit :
On 17 July 2013 15:19, Emmanuel Lécharny elecha...@gmail.com
wrote:
With SVN the way I do it is:
We don't use SVN anymore.
I realise that.
Maybe Git offers functionality that would allow a similar approach
which achieves the same goals:
- don't leave trunk
Thanks Jeff ! I think we should try it next time which should be soon in a
Milestone cycle.
Le 18 juil. 2013 00:31, Jeff MAURY jeffma...@jeffmaury.com a écrit :
The release plugin has a pushChanges flag for git which is true by default
for preserving compatibility but could be useful.
Jeff
[
https://issues.apache.org/jira/browse/SSHD-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet reopened SSHD-138:
--
Fresh git clone failed on ScpTest testWithGanymede
1 - 100 of 154 matches
Mail list logo
