|
On 11th February 2010 the latest release candidate for Git v1.7.0 was made available for download and testing.
This is hoped to be the final Git release candidate before the official production release of Git 1.7.0 expected in the next few days.
The download is available from the normal git release points:
http://www.kernel.org/pub/software/scm/git/
git-1.7.0.rc2.tar.{gz,bz2} (source tarball)
git-htmldocs-1.7.0.rc2.tar.{gz,bz2} (preformatted docs)
git-manpages-1.7.0.rc2.tar.{gz,bz2} (preformatted docs)
The RPM binary packages for a few architectures are found in:
testing/git-*-1.7.0.rc2-1.fc11.$arch.rpm (RPM)
Clearvision provide Git Training (including Git eLearning), Git Support for both large and small organisations, Git Consulting and also Git related products such as our Application Lifecycle Management interface for Git Agile UCM4Git.
Details of the Release can be found in the Release Notes below:
Git v1.7.0 Release Notes (draft)
========================
Notes on behaviour change
-------------------------
-
"git push" into a branch that is currently checked out (i.e. pointed by
HEAD in a repository that is not bare) is refused by default.
Similarly, "git push $there :$killed" to delete the branch $killed
in a remote repository $there, when $killed branch is the current
branch pointed at by its HEAD, will be refused by default.
Setting the configuration variables receive.denyCurrentBranch and
receive.denyDeleteCurrent to 'ignore' in the receiving repository
can be used to override these safety features.
-
"git send-email" does not make deep threads by default when sending a
patch series with more than two messages. All messages will be sent
as a reply to the first message, i.e. cover letter.
It has been possible to configure send-email to send "shallow thread"
by setting sendemail.chainreplyto configuration variable to false. The
only thing this release does is to change the default when you haven't
configured that variable.
-
"git status" is not "git commit --dry-run" anymore. This change does
not affect you if you run the command without argument.
-
"git diff" traditionally treated various "ignore whitespace" options
only as a way to filter the patch output. "git diff --exit-code -b"
exited with non-zero status even if all changes were about changing the
amount of whitespace and nothing else. and "git diff -b" showed the
"diff --git" header line for such a change without patch text.
In this release, the "ignore whitespaces" options affect the semantics
of the diff operation. A change that does not affect anything but
whitespaces is reported with zero exit status when run with
--exit-code, and there is no "diff --git" header for such a change.
-
External diff and textconv helpers are now executed using the shell.
This makes them consistent with other programs executed by git, and
allows you to pass command-line parameters to the helpers. Any helper
paths containing spaces or other metacharacters now need to be
shell-quoted. The affected helpers are GIT_EXTERNAL_DIFF in the
environment, and diff.*.command and diff.*.textconv in the config
file.
-
The --max-pack-size argument to 'git repack', 'git pack-objects', and
'git fast-import' was assuming the provided size to be expressed in MiB,
unlike the corresponding config variable and other similar options accepting
a size value. It is now expecting a size expressed in bytes, with a possible
unit suffix of 'k', 'm', or 'g'.
|
|
Clearvision have launched a facebook page with the latest software change and configuration management news along with updates for Clearvision products such as Agile UCM for Subversion and our ClearCase to Subversion migration tool Migrate2SVN.
Click on the facebook logo below to be taken to the Clearvision page and register as a fan.
 |
|
The latest version of Intlands award winning ALM software codeBeamer, has been released with a number of exciting new features.
In response to changing demands in the marketplace codeBeamer has added support for the Distributed Version Control Systems (DVCS) Mercurial (hg) and Git.
Git secures the Linux kernel and Googles Android operating System.
Mercurial is used by Mozilla, Python and Open Office.
CodeBeamer 5.4 has enhanced its processing to address these repositories which can contain several gigabytes of code and hundreds of thousands of change sets.
In addition to these improvements codebeamer 5.4 adds the following features:
- Issue escalation with hierarchic working calendars
- Calculated tracker fields with rich formula
- Wiki page editing directly in Microsoft Word
- Scalable version control management
- Major enhancements in supporting Git and Mercurial
- Revised search: more relevancy, richer query syntax, friendlier interface
Clearvision provide Git Training, Git Support, Git Consulting and Git Products such as our Git Agile Application Lifecycle Management solution UCMGIT.
Clearvision also provide services and licences for Intland Codebeamer in addition to services for Mercurial. |
|
Intland have recently announced the release of their small development team version of codeBeamer, Managed Repositories or MR, with the exciting news that it is a Free Forever release.
“codeBeamer Managed Repositories (MR) is the perfect mix of simplified Source Code Repository Management, Issue Tracking and Project Management. Components of MR have been battle tested for years by large corporations that rely on codeBeamer, the Jolt award winning Collaborative ALM software from Intland.
Now we are enabling smaller teams to benefit from it.
codeBeamer Managed Repositories is free. Forever.
WHO IS IT FOR?
For development teams working with Subversion, Git or Mercurial and striving for consistent access control, codeBeamer MR provides easy-to-use repository management. With its unified project-, group-, and role-based administration capabilities across multiple repositories, it makes it very efficient to control access rights. |
|
|
|
<< Start < Prev 1 2 3 4 5 6 7 8 9 10 Next > End >>
|
|
Page 1 of 11 |