Posted
about 1 month
ago
by
Corey Trager
BugTracker.NET is a free, open-source, GPL, ASP.NET bug tracking app.
More info at http://ifdefined.com/bugtrackernet.html
With the integration, if you do a commit like...
git commit -a -m "123 fixed the bug"
...then the hook
... [More]
script will link up the commit to bug 123.
Here are screenshots of the Subversion integration, which looks pretty much like the git integration:
http://ifdefined.com/doc_bug_tracker_subversion.html
Feedback very welcome, good or bad.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]
Posted
about 1 month
ago
by
Catalin Marinas
StGit is a Python application providing functionality similar to Quilt
(i.e. pushing/popping patches to/from a stack) on top of Git. These
operations are performed using Git commands, and the patches are
stored as Git commit objects
... [More]
, allowing easy merging of the StGit
patches into other repositories using standard Git functionality.
Download: http://download.gna.org/stgit/stgit-0.15.tar.gz
Main repository: git://repo.or.cz/stgit.git
Project homepage: http://www.procode.org/stgit/
Mailing list: git@vger.kernel.org (please use "StGit" in the subject)
Bug tracker: https://gna.org/bugs/?group=stgit
The main changes since release 0.14.3 are
- New core infrastructure for repository operations, including
+ Infinite undo/redo operations and corresponding commands.
+ Automatic rollback of changes following a failed operation
(using transactions)---this ensures that StGit commands either
succeed or do nothing. Previously, every commands had its own
ad hoc implementation of this.
- Some commands were added, including
+ "stg squash", for combining two or more patches into one.
+ "stg publish", for maintaining merge-friendly branches (which
are not rebased).
+ "stg prev/next" for printing the name of the previous or next
patch in the series.
- The commands "stg add", "stg rm", "stg cp", and "stg resolved"
were removed, since there are corresponding Git equivalents.
- The "stg import" and "stg fold" commands support the "-p N" option
for stripping leading slashes from diff paths.
- The "stg import" and "stg fold" commands support the "--reject"
option for leaving rejected hunks in corresponding *.rej files.
- New patch identification syntax: : (see
documentation for the "stg id" command).
- Autosigning of imported patches when "sign.autosign" configuration
option is set.
- A powerful Emacs mode for StGit was added to the "contrib"
directory. It displays the patch stack in an Emacs buffer, and can
handle all common StGit tasks.
- Improved bash tab-completion, automatically generated from the stg
command definitions.
- Man pages and an improved tutorial.
Special thanks go to Karl Wiberg for the hard work done on the new
StGit features, to Catalin Marinas for many new features and bugfixes,
and to David K [Less]
Posted
about 1 month
ago
by
Frank Li
Download:
http://tortoisegit.googlecode.com/files/TortoiseGit-1.1.1.0-32bit.msi
http://tortoisegit.googlecode.com/files/TortoiseGit-1.1.1.0-64bit.msi
= Release 1.1.1.0 =
== Features ==
* Improve Rebase Dialog
Allow
... [More]
lanuch new rebase dialog again after finish rebase dialog
Disable "force rebase" checkbox during rebase.
* Git SVN
Append svn:ignore settings to the default git exclude file Add
shell extension command to import svn ignore settings.
Need press "Shift" key to show "import svn ignore" command.
* Drag-drop copy\move support
File only
* Add paste command at shell extension
Copy and paste file is okay. But there are problems when including
directory.
Cut and paste working
* Update notepad2 to 4.022
* Sync Dialog
Ability to sync submodules in TGit sync dialog
* Statics
Sort commits by dates before processed by StatGraphDlg
* Log Dialog
Show replace ref error message at log dialog
* Add Check software updater support.
== Bug Fix ==
* Fixed issue #185. "Can't find Super-project" when pathname include space.
* Fixed issue #190: Access violation in Blame and wrong path name
when root dir is git repository
* Fixed issue #180: Create patch serial doesn't work when there is
"\" at end of path
* Fixed issue #173: SVN Rebase does not work The correct handle below
case git config svn-remote.svn.fetch
myproject/trunk:refs/remotes/trunk
* Fixed issue #169: Force rebase checkbox is fixed
* Fixed issue #163: Conflict "theirs" and "mine" are reversed during a rebase
* Fixed issue #165: Incorect path to Notepad2
* Fixed issue #158: Rebase can act on the wrong branch
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]
Posted
about 1 month
ago
by
Junio C Hamano
The latest maintenance release GIT 1.6.5.1 is available at the
usual places:
http://www.kernel.org/pub/software/scm/git/
git-1.6.5.1.tar.{gz,bz2} (source tarball)
git-htmldocs-1.6.5.1.tar.{gz,bz2} (preformatted
... [More]
docs)
git-manpages-1.6.5.1.tar.{gz,bz2} (preformatted docs)
The RPM binary packages for a few architectures are found in:
RPMS/$arch/git-*-1.6.5.1-1.fc9.$arch.rpm (RPM)
GIT v1.6.5.1 Release Notes
==========================
Fixes since v1.6.5
------------------
* An corrupt pack could make codepath to read objects into an
infinite loop.
* Download throughput display was always shown in KiB/s but on fast links
it is more appropriate to show it in MiB/s.
* "git grep -f filename" used uninitialized variable and segfaulted.
* "git clone -b branch" gave a wrong commit object name to post-checkout
hook.
* "git pull" over http did not work on msys.
Other minor documentation updates are included.
----------------------------------------------------------------
Changes since v1.6.5 are as follows:
Björn Steinbrink (1):
clone: Supply the right commit hash to post-checkout when -b is used
Johannes Sixt (1):
remote-curl: add missing initialization of argv0_path
Junio C Hamano (1):
GIT 1.6.5.1
Matt Kraai (1):
grep: do not segfault when -f is used
Miklos Vajna (1):
git-stash documentation: mention default options for 'list'
Nicolas Pitre (1):
change throughput display units with fast links
Shawn O. Pearce (1):
sha1_file: Fix infinite loop when pack is corrupted
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]
Posted
about 1 month
ago
by
Meinrad Recheis
Hello git community,
GitSharp intends to bring best native git support to Windows. So far
the command line interface is still alpha but the library
GitSharp.Core is already quite usable.
Status Report:
Porting of the jgit core is done, we are waiting for the jgit people
to commit something
Posted
about 1 month
ago
by
Junio C Hamano
The latest feature release GIT 1.6.5 is available at the usual
places:
http://www.kernel.org/pub/software/scm/git/
git-1.6.5.tar.{gz,bz2} (source tarball)
git-htmldocs-1.6.5.tar.{gz,bz2} (preformatted
... [More]
docs)
git-manpages-1.6.5.tar.{gz,bz2} (preformatted docs)
The RPM binary packages for a few architectures are found in:
RPMS/$arch/git-*-1.6.5-1.fc9.$arch.rpm (RPM)
This cycle took a bit longer than I hoped, but here it is. We already
have some new features cooking in 'next', and I expect we may be able to
have 1.6.6 by the end of the year.
Enjoy.
----------------------------------------------------------------
GIT v1.6.5 Release Notes
========================
In git 1.7.0, which was planned to be the release after 1.6.5, "git
push" into a branch that is currently checked out will be refused by
default.
You can choose what should happen upon such a push by setting the
configuration variable receive.denyCurrentBranch in the receiving
repository.
Also, "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.
You can choose what should happen upon such a push by setting the
configuration variable receive.denyDeleteCurrent in the receiving
repository.
To ease the transition plan, the receiving repository of such a
push running this release will issue a big warning when the
configuration variable is missing. Please refer to:
http://git.or.cz/gitwiki/GitFaq#non-bare
http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
for more details on the reason why this change is needed and the
transition plan.
Updates since v1.6.4
--------------------
(subsystems)
* various updates to gitk, git-svn and gitweb.
(portability)
* more improvements on mingw port.
* mingw will also give FRSX as the default value for the LESS
environment variable when the user does not have one.
* initial support to compile git on Windows with MSVC.
(performance)
* On major platforms, the system can be compiled to use with Linus's
block-sha1 implementation of the SHA-1 hash algorithm, which
outperforms the default fallback implementation we borrowed from
Mozilla.
* Unnecessary inefficiency in deepening of a shallow repository has
been removed.
* "git clone" does not grab objects that it does not need (i.e.
referenced only from refs outside refs/heads and refs/tags
hierarchy) anymore.
* The "git" main binary used to link with libcurl, which then dragged
in a large number of external libraries. When using basic plumbing
commands in scripts, this unnecessarily slowed things down. We now
implement http/https/ftp transfer as a separate executable as we
used to.
* "git clone" run locally hardlinks or copies the files in .git/ to
newly created repository. It used to give new mtime to copied files,
but this delayed garbage collection to trigger unnecessarily in the
cloned repository. We now preserve mtime for these files to avoid
this issue.
(usability, bells and whistles)
* Human writable date format to various options, e.g. --since=yesterday,
master@{2000.09.17}, are taught to infer some omitted input properly.
* A few programs gave verbose "advice" messages to help uninitiated
people when issuing error messages. An infrastructure to allow
users to squelch them has been introduced, and a few such messages
can be silenced now.
* refs/replace/ hierarchy is designed to be usable as a replacement
of the "grafts" mechanism, with the added advantage that it can be
transferred across repositories.
* "git am" learned to optionally ignore whitespace differences.
* "git am" handles input e-mail files that has CRLF line endings sensibly.
* "git am" learned "--scissors" option to allow you to discard early part
of an incoming e-mail.
* "git archive -o output.zip" works without being told what format to
use with an explicit "--format=zip".option.
* "git checkout", "git reset" and "git stash" learned to pick and
choose to use selected changes you made, similar to "git add -p".
* "git clone" learned a "-b" option to pick a HEAD to check out
different from the remote's default branch.
* "git clone" learned --recursive option.
* "git clone" from a local repository on a different filesystem used to
copy individual object files without preserving the old timestamp, giving
them extra lifetime in the new repository until they gc'ed.
* "git commit --dry-run $args" is a new recommended way to ask "what would
happen if I try to commit with these arguments."
* "git commit --dry-run" and "git status" shows conflicted paths in a
separate section to make them easier to spot during a merge.
* "git cvsimport" now supports password-protected pserver access even
when the password is not taken from ~/.cvspass file.
* "git fast-export" learned --no-data option that can be useful when
reordering commits and trees without touching the contents of
blobs.
* "git fast-import" has a pair of new front-end in contrib/ area.
* "git init" learned to mkdir/chdir into a directory when given an
extra argument (i.e. "git init this").
* "git instaweb" optionally can use mongoose as the web server.
* "git log --decorate" can optionally be told with --decorate=full to
give the reference name in full.
* "git merge" issued an unnecessarily scary message when it detected
that the merge may have to touch the path that the user has local
uncommitted changes to. The message has been reworded to make it
clear that the command aborted, without doing any harm.
* "git push" can be told to be --quiet.
* "git push" pays attention to url.$base.pushInsteadOf and uses a URL
that is derived from the URL used for fetching.
* informational output from "git reset" that lists the locally modified
paths is made consistent with that of "git checkout $another_branch".
* "git submodule" learned to give submodule name to scripts run with
"foreach" subcommand.
* various subcommands to "git submodule" learned --recursive option.
* "git submodule summary" learned --files option to compare the work
tree vs the commit bound at submodule path, instead of comparing
the index.
* "git upload-pack", which is the server side support for "git clone" and
"git fetch", can call a new post-upload-pack hook for statistics purposes.
(developers)
* With GIT_TEST_OPTS="--root=/p/a/t/h", tests can be run outside the
source directory; using tmpfs may give faster turnaround.
* With NO_PERL_MAKEMAKER set, DESTDIR= is now honoured, so you can
build for one location, and install into another location to tar it
up.
Fixes since v1.6.4
------------------
All of the fixes in v1.6.4.X maintenance series are included in this
release, unless otherwise noted.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]
Posted
2 months
ago
by
Meinrad Recheis
Hello git community,
Thanks to our active development community git# is quickly making
progress. The library GitSharp.dll is about 95% complete and we have
started creating a command line interface which shall be equivalent
... [More]
to
the original git. It already executes the commands "init" and "clone"
(not yet via SSH), some other commands are prepared as stubs. Please
note that not yet all tests are passing and that we are still working
on porting over jgit's changes from the last few months.
Download the binaries and find more information about this release at
http://www.eqqon.com/index.php/GitSharp/v0.1.0
Enjoy our first release and have a nice weekend,
-- henon
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]
Posted
3 months
ago
by
Uwe =?iso-8859-1?Q?Kleine-K=F6nig?=
Hello,
I'm happy to announce that TopGit 0.8 was released today.
TopGit aims to make handling of large amount of interdependent topic
branches easier. In fact, it is designed especially for the case when
you maintain a queue
... [More]
of third-party patches on top of another (perhaps
Git-controlled) project and want to easily organize, maintain and submit
them - TopGit achieves that by keeping a separate topic branch for each
patch and providing few tools to maintain the branches
It has been a bit silent around TopGit for some time. Still a few
patches accumulated since the last relase. To get them out I have made
this release.
The highlight is a new command tg-push that makes pushing topgit
branches more comfortable. Thanks to Marc Weber and Bert Wesarg.
Other than that there are quite a few bugfixes.
If ever you have problems with or suggestions for or need for discussion
about TopGit, join us in #topgit in the freenode irc network.
As usual the release is available at
http://repo.or.cz/w/topgit.git
I will talk to martin to get this release into Debian/unstable soon.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K [Less]
Posted
3 months
ago
by
Intland Software
If you're using Git, and you need an issue tracker, wiki, doc
management, project management that tightly integrates with your
favourite git and somewhat resembles of GitHub-behind-a-firewall, then
you might be interested in this. If not
... [More]
, then we apologize.
codeBeamer 5.4 is the latest and greatest version of our collaborative
Application Lifecycle Management software
(http://www.intland.com/products/cb/overview.html).
Links:
* Product homepage: http://www.intland.com/products/cb/overview.html
* Download (no expiration!):
http://www.intland.com/products/download.html#download
* Hosted version: http://www.intland.com/products/download.html#trial
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]
Posted
3 months
ago
by
Junio C Hamano
The latest maintenance release GIT 1.6.4.4 is available at the
usual places:
http://www.kernel.org/pub/software/scm/git/
git-1.6.4.4.tar.{gz,bz2} (source tarball)
git-htmldocs-1.6.4.4.tar.{gz,bz2} (preformatted
... [More]
docs)
git-manpages-1.6.4.4.tar.{gz,bz2} (preformatted docs)
The RPM binary packages for a few architectures are found in:
RPMS/$arch/git-*-1.6.4.4-1.fc9.$arch.rpm (RPM)
This is primarily to fix a http regression introduced by 1.6.4.3
GIT v1.6.4.4 Release Notes
==========================
Fixes since v1.6.4.4
--------------------
* The workaround for Github server that sometimes gave 500 (Internal server
error) response to HEAD requests in 1.6.4.3 introduced a regression that
caused re-fetching projects over http to segfault in certain cases due
to uninitialized pointer being freed.
* "git pull" on an unborn branch used to consider anything in the work
tree and the index discardable.
* "git diff -b/w" did not work well on the incomplete line at the end of
the file, due to an incorrect hashing of lines in the low-level xdiff
routines.
* "git checkout-index --prefix=$somewhere" used to work when $somewhere is
a symbolic link to a directory elsewhere, but v1.6.4.2 broke it.
* "git unpack-objects --strict", invoked when receive.fsckobjects
configuration is set in the receiving repository of "git push", did not
properly check the objects, especially the submodule links, it received.
Other minor documentation updates are included.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]
