From: Ben Armstrong <BArmstrong@dymaxion.ca>
To: git@vger.kernel.org
Subject: Re: jgit standalone client on OpenVMS works (somewhat)
Date: Fri, 1 May 2009 07:08:38 -0300 [thread overview]
Message-ID: <3f1ae6620905010308u44be6aefl5dccf0901424c292@mail.gmail.com> (raw)
Shawn O. Pearce wrote:
> > I'm talking to some folks who are trying to put JGit into Maven.
> > They want to move a lot of egit.core down into JGit, which should
> > make it easier to add more commands to the jgit wrapper, making a
> > more functional command line tool.
Certainly without at least commit (and diff would be nice) I can't go
any further with jgit on VMS today. We will have to use jsvn for the
interim (our repositories are currently in svn anyway, and jsvn is
reasonably full-featured and functional on VMS). But it's nice to have
a migration path in the offing.
> > Can you write a subclass of our FS class that can identify a
> > VMS host and use that VMS specific subclass?
> >
Should I return to jgit, I could look into this (though I am not a Java
programmer).
> > If so, we could add a method, e.g.:
> >
> > boolean canBeLooseRef(String name)
> >
> > and on VMS when the name falls into that "ODS-5_Syntax
> > Interpretation_of_Period" rule set above, we could return false.
> > This would then permit a simple change in RefDatabase where we always
> > store such refs in the packed-refs file, instead of as a loose file.
> >
> > It also means we'd have to forgo the ref log, or mangle the reflog
> > name.
> >
> > But it seems to me we could reasonably work around this without
> > too much trouble.
> >
Glad to hear it. I have taken note in case I revive this effort later.
Before I sign off entirely, I'd like to mention also that I tried using
the ssh protocol without success:
A:BG.WORK> git clone ssh://ben@bgpc.dymaxion.ca/home/ben/git/myrepo.git
Initialized empty Git repository in /DSA0/BG/WORK/myrepo/.git
java.lang.NullPointerException
at com.jcraft.jsch.Session.disconnect(Session.java)
at
org.spearce.jgit.transport.SshSessionFactory.releaseSession(SshSessionFactory.java)
at org.spearce.jgit.transport.SshTransport.close(SshTransport.java)
at org.spearce.jgit.pgm.Clone.runFetch(Clone.java)
at org.spearce.jgit.pgm.Clone.run(Clone.java)
at org.spearce.jgit.pgm.TextBuiltin.execute(TextBuiltin.java)
at org.spearce.jgit.pgm.Main.execute(Main.java)
at org.spearce.jgit.pgm.Main.main(Main.java)
$ dir [.myrepo.^.git...]
Directory DSA0:[BG.WORK.myrepo.^.git]
branches.DIR;1 config.;3 HEAD.;1
objects.DIR;1
refs.DIR;1 remotes.DIR;1
Total of 6 files.
Directory DSA0:[BG.WORK.myrepo.^.git.objects]
info.DIR;1 pack.DIR;1
Total of 2 files.
Directory DSA0:[BG.WORK.myrepo.^.git.refs]
heads.DIR;1 tags.DIR;1
Total of 2 files.
Grand total of 3 directories, 10 files.
next reply other threads:[~2009-05-01 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-01 10:08 Ben Armstrong [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-30 15:39 jgit standalone client on OpenVMS works (somewhat) Ben Armstrong
2009-04-30 19:26 ` Shawn O. Pearce
2009-05-03 15:15 ` Robin Rosenberg
[not found] ` <49FEE276.8010508@gmail.com>
2009-05-04 12:42 ` Ben Armstrong
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=3f1ae6620905010308u44be6aefl5dccf0901424c292@mail.gmail.com \
--to=barmstrong@dymaxion.ca \
--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.
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).