From: "Shawn O. Pearce" <spearce@spearce.org>
To: "J. Longman" <longman@xiplink.com>
Cc: git@vger.kernel.org
Subject: Re: jgit as a jira plugin
Date: Wed, 29 Oct 2008 16:53:17 -0700 [thread overview]
Message-ID: <20081029235317.GC31926@spearce.org> (raw)
In-Reply-To: <D7D18CE8-BDBD-430A-BCB6-D1BEFD21C949@xiplink.com>
"J. Longman" <longman@xiplink.com> wrote:
> Basically I stole the pgm.Fetch code:
>
> Transport tn = Transport.open(repository, "origin");
> final FetchResult r;
> List<RefSpec> toget = new ArrayList<RefSpec>();
> try {
> r = tn.fetch(new TextProgressMonitor(), toget);
> } finally {
> tn.close();
> }
>
> Can I assume that this enough to update the database?
Yes
> After this (and not shown) is some
> logging code taken from Fetch, which results in the following:
>
> From /Users/longman/workspace2/work/../masterRepo/
> 131dcf5..078d43f master -> origin/master
>
> but there doesn't appear to be any specific mention of the incoming
> changes.
Well, the new changes are what "git log 131dcf5..078d43f" outputs.
--
Shawn.
next prev parent reply other threads:[~2008-10-29 23:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 23:02 jgit as a jira plugin J. Longman
2008-10-29 23:08 ` Shawn O. Pearce
2008-10-29 23:49 ` J. Longman
2008-10-29 23:53 ` Shawn O. Pearce [this message]
[not found] ` <C9B1B0D7-6F99-48DE-8593-A13F1187ADE2@xiplink.com>
2008-10-31 14:42 ` 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=20081029235317.GC31926@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=longman@xiplink.com \
/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).