| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Many operations that act on history, including ``log`` and ``annotate`` are
now substantially faster. Several bugs have been fixed and several new
options and features have been added.
And more, please review the NEWS file.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
GIT v1.5.4.5 Release Notes
==========================
Fixes since v1.5.4.4
--------------------
* "git fetch there" when the URL information came from the Cogito style
branches/there file did not update refs/heads/there (regression in
1.5.4).
* Bogus refspec configuration such as "remote.there.fetch = =" were not
detected as errors (regressionin 1.5.4).
* You couldn't specify a custom editor whose path contains a whitespace
via GIT_EDITOR (and core.editor).
* The subdirectory filter to "git filter-branch" mishandled a history
where the subdirectory becomes empty and then later becomes non-empty.
* "git shortlog" gave an empty line if the original commit message was
malformed (e.g. a botched import from foreign SCM). Now it finds the
first non-empty line and uses it for better information.
* When the user fails to give a revision parameter to "git svn", an error
from the Perl interpreter was issued because the script lacked proper
error checking.
* After "git rebase" stopped due to conflicts, if the user played with
"git reset" and friends, "git rebase --abort" failed to go back to the
correct commit.
* Additional work trees prepared with git-new-workdir (in contrib/) did
not share git-svn metadata directory .git/svn with the original.
* "git-merge-recursive" did not mark addition of the same path with
different filemodes correctly as a conflict.
* "gitweb" gave malformed URL when pathinfo stype paths are in use.
* "-n" stands for "--no-tags" again for "git fetch".
* "git format-patch" did not detect the need to add 8-bit MIME header
when the user used format.header configuration.
* "rev~" revision specifier used to mean "rev", which was inconsistent
with how "rev^" worked. Now "rev~" is the same as "rev~1" (hence it
also is the same as "rev^1"), and "rev~0" is the same as "rev^0"
(i.e. it has to be a commit).
* "git quiltimport" did not grok empty lines, lines in "file -pNNN"
format to specify the prefix levels and lines with trailing comments.
* "git rebase -m" triggered pre-commit verification, which made
"rebase --continue" impossible.
As usual, it also comes with many documentation fixes and clarifications.
|
|
|
|
|
|
Packages Collection.
Mocha is a Ruby library for mocking and stubbing using a syntax
like that of JMock, and SchMock. Most commonly Mocha is used in
conjunction with Test::Unit, but it can be used in other contexts.
One of its main advantages is that it allows you to mock and stub
methods on real (non-mock) classes and instances. You can for
example stub ActiveRecord instance methods like create, save,
destroy and even class methods like find to avoid hitting the
database in unit tests.
Mocha provides a unified, simple and readable syntax for both
traditional mocking and for mocking with real objects.
|
|
|
|
Packages Collection.
Ruby-debug-ide provides an interface which glues ruby-debug to IDEs
like Eclipse (RDT) and NetBeans.
|
|
Packages Collection.
Command line interface for the Ruby debugger ruby-debug.
|
|
Packages Collection.
Ruby-debug is a faster implementation of the standard Ruby debugger
debug.rb using a native extension with a new hook Ruby C API.
|
|
No C compiler required.
|
|
A C compiler is required.
|
|
No C compiler required.
This is an UNAUTHORIZED RELEASE (according to search.cpan.org), so we
cannot use the author-independent URL for HOMEPAGE.
|
|
Pkgsrc changes:
- The packages supports installation to DESTDIR.
- No C compiler required.
- Needs more modern version of p5-Devel-StackTrace.
Changes since version 1.23:
===========================
1.24 Mar 30, 2008
- Added a MaxArgLength class parameter to go along with the new
max_arg_length constructor param for Devel::StackTrace
objects. Patch by Ian Burrell.
|
|
Pkgsrc changes:
- The package supports installation to DESTDIR.
- A C compiler is not required.
Changes since version 0.06:
===========================
0.08 Sat Jan 26 00:34:11 NZDT 2008
- Fix 'perltooc' typo in Docs
0.07 Sat Jan 26 00:34:11 NZDT 2008
- Relicense as dual AL/GPL
|
|
Pkgsrc changes:
- Used author-independent URL for HOMEPAGE.
- The package supports installation to DESTDIR.
- A C compiler is not required.
Changes since version 1.15:
===========================
1.18 Mar 31, 2008
- Fix a test failure on Win32. No changes to the non-test code.
1.17 Mar 30, 2008
- Added a max_arg_length parameter, which if set causes
Devel::StackTrace to truncate long strings when printing out a
frame. RT #33519. Patch by Ian Burrell.
1.16 Feb 2, 2008
- A test fix for bleadperl. The value of wantarray from caller() needs
to be treated as a boolean, as opposed to expecting 0 (vs
undef). RT #32583. Patch by Jerry Hedden.
|
|
A C compiler is not needed.
|
|
Pkgsrc changes:
- Provided HOMEPAGE.
- The package supports installation to DESTDIR.
- A C compiler is needed.
- The "Configure" script has been removed, so we do not have tell it to use
defaults (part of patch-aa) or change its stdin in MAKE_PARAMS anymore.
- sharelite.c has been renamed upstream, no more need to do this in pkgsrc,
thus making patch-aa and patch-ab obsolete.
Changes since version 0.09:
===========================
0.13 2008-03-09
- Fixed patching of double quoted strings in Makefile. Affects Win32
and, probably, VMS.
0.12 2008-02-25
- Use Devel::CheckLib to verify that we have a C compiler.
0.11 2008-02-25
- Removed POD coverage test. Dynamic constants make it flaky.
0.10 2008-02-24
- Use Perl's malloc wrappers
- moved test into t/sharelite.t
- made test use Test::More
- removed Configure mechanism
- assorted minor tidying
|
|
|
|
see the git history by checking out the repository at the address
provided at the homepage.
|
|
This release contains a lot of bug-fixes and some new features. Please see http://src.opensolaris.org/source/history/opengrok/trunk/ for the full change history, and for the list of contributors. The following is just a summary.
New Features:
* Analyzer-support for Tcl/Tk
* Analyzer-support for SQL
* Support for TeamWare repositories
|
|
- updates of generated files and gnulib components
- minor documentation fixes.
This update was originally done by Blair Sadewitz.
|
|
|
|
- Added two missing header files: fmt/misc.h and fmt/multi.h
- Added a ghash_set function (like ghash_add, but overwrites).
- Added a set of "signalfd" functions as a generic self-pipe setup.
- Added a random number generator based on SURF.
|
|
|
|
path to these directories.
|
|
directly into site_ruby.
|
|
|
|
The ruby-memcache package is a wrapper around memcache(3) and provides
exceptionally fast access to a memcached(8) cluster.
|
|
|
|
+ Install as a Ruby gem.
* Update for Ruby 1.9.0.
* New type_id values will merge with extant data. (self-repairing data is Good)
* Scrape processor_ids, merging in with extant data.
* Default to "Other" if a file's type is unrecognized.
* Set mode on .rubyforge directory to 700.
* Fix fetching of user id when user has no releases.
|
|
ruby2ruby provides a means of generating pure ruby code easily from
ParseTree's Sexps. This makes making dynamic language processors much
easier in ruby than ever before.
|
|
The validatable library can be included with any Ruby class and provide
validations similar to ActiveRecord's. The library follows ActiveRecord's
lead for features that are similar and introduces new features.
|
|
test/spec layers an RSpec-inspired interface on top of Test::Unit, so
you can mix TDD and BDD (Behavior-Driven Development).
|
|
RSpec is a Behaviour Driven Development framework for Ruby. It provides
two frameworks for writing and executing examples of how your Ruby
application should behave:
* a Story Framework for describing behaviour at the application level
* a Spec Framework for describing behaviour at the object level
|
|
+ Install as a Ruby gem.
* All IDs for DOT objects, including names, options, and values, are
now automatically quoted as necessary for graphviz. Labels are
handled specially in order to account for \l, \r, and \n sequences
but are otherwise treated the same as other options. Some changes
were made in order to remove explicit quotes from labels which are
no longer necessary.
* Removed backwards compatability method inject.
* DOTSimpleElement provides no useful function, so remove it
* Add support for the Mrecord shape to DOTNode. Rewrite DOTNode#to_s
to be easier to understand. #Rewrite DOTPort to allow for nesting
ports.
* DOTElement no longer sets the label unless the user explicitly sets
one.
* Subgraphs must be identified by a "subgraph" header rather than a
"graph" header
* Added equality test for graphs, added cycle locating. Modified
initialize to allow duplicating and merging of graphs.
* Assorted bug fixes.
|
|
Ruby-rcov is a code coverage tool for Ruby. It is commonly used for
viewing overall test unit coverage of target code. It features fast
execution (20-300 times faster than previous tools), multiple analysis
modes, XHTML and several kinds of text reports, easy automation with
Rake via a RcovTask, fairly accurate coverage information through code
linkage inference using simple heuristics, and colorblind-friendliness.
|
|
ParseTree is a C extension (using RubyInline) that extracts the parse
tree for an entire class or a specific method and returns it as a
s-expression (aka sexp) using ruby's arrays, strings, symbols, and
integers.
|
|
Needle is a Dependency Injection/Inversion of Control container for
Ruby. It supports both type-2 (setter) and type-3 (constructor)
injection. It takes advantage of the dynamic nature of Ruby to provide
a rich and flexible approach to injecting dependencies.
|
|
mkrf is a library for generating Rakefiles. It is primarily for
building C extensions for Ruby, but will be able to be used for generic
Rakefile generation as well. Main goals include simple use and reuse
in other projects.
|
|
MetAid adds a few innocent methods to Object and Module to make
metaprogramming easier. For the lore of metaprogramming see Seeing
Metaclasses Clearly and Chapter Six of Why's (Poignant) Guide to Ruby.
|
