From: Robin Rosenberg <robin.rosenberg@dewire.com>
To: git@vger.kernel.org
Subject: The EGIT Chronicles Issue Volume 2, Issue 1
Date: Sun, 2 Mar 2008 01:51:28 +0100 [thread overview]
Message-ID: <200803020151.28397.robin.rosenberg@dewire.com> (raw)
Eclipse 0.3.1 is out
This release contains a number of minor features and bug fixes.
Features:
- Resources are now decorated with repository state, e.g. whether a merge or
rebase is in progress.
- Better (subject to subjectivity) formatting of tooltips in the history view
- Actions to set/reset the assume valid bit for files, including decorations
- Improved layout of the history pane and user preferences for this
- Simpler layout of changed files in the compare editor, i.e. we do not list
folders anymore, just changed files.
- Searching in the history view
Bug fixes:
- Bugfixes related to checkout and detection of changed files for commit. This
is the most important part of this release.
- The ability to perform the first commit in a repository from within Eclipse.
- Parsing of the config file
Documentation:
- Javadoc on anything public/protected in jgit. Should make it a little easier
for newcomers. Also makes the project look better on Ohloh. Unit tests for
jgit moved into it's own project and tests that do require external
dependencies were separated from better defined ones that do not.
- A number of typo's fixed.
New branch:
- Created stable branch. Currently points to v0.3.1. This branch will contain
tagged versions.
Special thanks to Roger C. Soares for the history and compare editor
improvements. Also thanks to Jing Xue, Ladislav Sladecek, Shunichi Fuji and
Vincent Legoll for correcting some smaller bugs and typos.
Next edition will contain at least fetch thanks to Shawn Pearce. I still have
a lot of loose ends to tie up before that happens. Roger Soares contributed
some GUI's for this.
-- robin
reply other threads:[~2008-03-02 0:51 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200803020151.28397.robin.rosenberg@dewire.com \
--to=robin.rosenberg@dewire.com \
--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).