git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Daniel Barkalow <barkalow@iabervon.org>
To: Shawn Pearce <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: Java GIT/Eclipse GIT version 0.1.1
Date: Sun, 30 Jul 2006 10:55:03 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0607301047150.9789@iabervon.org> (raw)
In-Reply-To: <20060728063620.GD30783@spearce.org>

On Fri, 28 Jul 2006, Shawn Pearce wrote:

> I would appreciate any and all input, feedback, etc. that anyone
> might have on this library or plugin.  Patches are of course
> certainly welcome.  :-)

I'm going to try to do a Servlet (+ my stuff) implementation of essentiall 
gitweb, with the idea that it could integrate with project management 
software (i.e., link completed tasks to the commit which completed them, 
regressions to the commit that broke things, fixes to the commit that 
fixed them, etc, with the UI for choosing values letting you browse the 
actual content and validating that the hash you give exists).

I don't think I need anything you don't already have, but I'll write 
documentation as I figure out what's going on, if you want that.

	-Daniel
*This .sig left intentionally blank*

  parent reply	other threads:[~2006-07-30 14:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-28  6:36 Java GIT/Eclipse GIT version 0.1.1 Shawn Pearce
2006-07-28  6:49 ` Peter Baumann
2006-07-28  7:08   ` Pavel Roskin
2006-07-28  7:23     ` Peter Baumann
2006-07-29  2:10       ` Pavel Roskin
2006-07-29 16:46         ` Peter Baumann
2006-07-29  3:32     ` Shawn Pearce
2006-07-29  3:55       ` Pavel Roskin
2006-07-29  4:08         ` Shawn Pearce
2006-07-29 10:15 ` Jakub Narebski
2006-07-30 14:55 ` Daniel Barkalow [this message]
2006-07-31  4:22   ` Shawn 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0607301047150.9789@iabervon.org \
    --to=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).