git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: git@vger.kernel.org
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
	David Watson <dwatson@mimvista.com>,
	Ben Konrath <bkonrath@redhat.com>
Subject: The EGIT Chronicles Issue Volume 1, Issue 2.
Date: Mon, 24 Sep 2007 01:06:18 +0200	[thread overview]
Message-ID: <200709240106.19595.robin.rosenberg.lists@dewire.com> (raw)


Version 0.3 of the Eclipse plugin is out. 

As the zero implies this plugin doesn't do everything, but it makes your 
coffee stronger.

FEATURES

Visualization:
	See the history graphically with highlighting for commits affected
	by the selected resource (Eclipse speak for file or directory).
	Resources are decorated with status.
	Branch name on projects
	Quick diff marks you latest changes visible and revertable in the editor

Actions:
	Connect to repositories
	Add, remove files, rename, update index
	Checkout including some cases of dirty work trees
	Compare revisions using the structured compare
	Commit files selectively, amend and sign-off commits

It even works on Windows, with either cygwin or msysgit (but doesn't do CRLF 
conversions) and OS X.

For advanced stuff you still need the "Real Git" (clone, push, fetch, merge 
etc).

Special thanks to Dave Watson for the Commit and checkout stuff and Shawn 
Pearce for making it possible by doing the initial work on the plugin and 
most importantly a fast pack reader that doesn't involve JNI. The base that 
Shawn formed made it possible to extend the plugin a small piece at a time 
without knowing very much about either Eclipse or Git internals.

BUGS
	Yes, probably.

URL:
	http://repo.or.cz/w/egit.git

-- robin

                 reply	other threads:[~2007-09-23 23:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200709240106.19595.robin.rosenberg.lists@dewire.com \
    --to=robin.rosenberg.lists@dewire.com \
    --cc=bkonrath@redhat.com \
    --cc=dwatson@mimvista.com \
    --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).