Git

The latest maintenance release Git 1.6.6.2 is available at the usual places: http://www.kernel.org/pub/software/scm/git/ git-1.6.6.2.tar.{gz,bz2} (source tarball) git-htmldocs-1.6.6.2.tar.{gz,bz2} (preformatted docs) ... [More] git-manpages-1.6.6.2.tar.{gz,bz2} (preformatted docs) The RPM binary packages for a few architectures are found in: RPMS/$arch/git-*-1.6.6.2-1.fc11.$arch.rpm (RPM) Git v1.6.6.2 Release Notes ========================== Fixes since v1.6.6.1 -------------------- * recursive merge didn't correctly diagnose its own programming errors, and instead caused the caller to segfault. * The new "smart http" aware clients probed the web servers to see if they support smart http, but did not fall back to dumb http transport correctly with some servers. * Time based reflog syntax e.g. "@{yesterday}" didn't diagnose a misspelled time specification and instead assumed "@{now}". * "git archive HEAD -- no-such-directory" produced an empty archive without complaining. * "git blame -L start,end -- file" misbehaved when given a start that is larger than the number of lines in the file. * "git checkout -m" didn't correctly call custom merge backend supplied by the end user. * "git config -f " misbehaved when run from a subdirectory. * "git cvsserver" didn't like having regex metacharacters (e.g. '+') in CVSROOT environment. * "git fast-import" did not correctly handle large blobs that may bust the pack size limit. * "git gui" is supposed to work even when launched from inside a .git directory. * "git gui" misbehaved when applying a hunk that ends with deletion. * "git imap-send" did not honor imap.preformattedHTML as documented. * "git log" family incorrectly showed the commit notes unconditionally by mistake, which was especially irritating when running "git log --oneline". * "git status" shouldn't require an write access to the repository. Other minor documentation updates are included. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]

Hi all, bup is a file backup tool based on the git packfile format. If you're interested in git, you might find bup interesting because: - It can handle really massive datasets (hundreds of gigabytes) without melting down. - It can handle huge ... [More] individual files (hundreds of gigabytes), such as virtual machine images or giant textual database dumps, while neither wasting disk space nor bogging down in xdelta. - It can backup files directly to a remote server, without creating git objects on the local system first. - It uses a different format for its index file (.bup/bupindex) that allows you to search and iterate non-linearly. Thus if you have a filesystem with a million files and only one of them is marked dirty, bup can back it up near-instantly. - Like git, it separates the concept of indexing the filesystem from the concept of actually making new commits. Thus it would be easy to plugin an inotify-like system eventually, avoiding the slow filesystem iteration every time you want to make a backup. - It introduces a "multi-index" file (midx) that has a sorted list of the objects from multiple .pack files, so that checking for a nonexistent object only needs to swap in two pages at most. (This is unimportant in git, but critical when most of your work is ingesting huge files whose sha1sums haven't been seen before.) - It provides a FUSE-based filesystem so that you can easily browse your backup history, including exporting it via samba if you want. bup doesn't yet back up extra file metadata (beyond what git already tracks). Obviously this will be needed relatively soon. bup is still pretty experimental, but it's already a useful tool for backing up your files, even if those files include millions of files and hundreds of gigs of VM images. You can find the source code (and README) at github: http://github.com/apenwarr/bup To subscribe to the bup mailing list, send an email to: [email protected] Looking forward to everyone's feedback. Have fun, Avery -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]

Gitolite is an ssh-based access control tool for using git in a typical "corporate" environment. The original goals were very simple: read/write/rewind access control at the git branch level, the ability to install on any Unix, no need for root ... [More] access, and no need for additional software (other than git and perl). There is plenty of documentation included with the source, because by now it has acquired a lot of features not originally planned. I now consider gitolite to be at 1.0, and this note summarises the features added since the last email to the list [1] about gitolite. Please see README.mkd and doc/3-faq-tips-etc.mkd for *all* the details if you are completely new to gitolite. * Install/upgrade can now be done even from the bash that comes with msysgit. This means pretty much anyone can quickly and easily install gitolite on any Unix server. * You can specify an "owner" and a "description" for gitweb to display. The syntax is very simple, here's an example: gitolite "Sitaram Chamarty" = "fast, secure, access control for git" * You can include any site-specific (custom) hooks that you want to propagate to any repo created by gitolite. * The "deny access" feature can be very useful sometimes; an example that shows how only bob may push version tags would look like this: @devs = alice bob charlie RW refs/tags/v[0-9] = bob - refs/tags/v[0-9] = @devs RW refs/tags/ = @devs More details can be found in the documentation. * Gitolite can now let you specify restrictions based on file/dir names (for example, restrict who can push changes that touch some file or directory). My initial response to this request was that this is better done by the social mechanisms of the project team, and I do not believe this feature is really necessary in a well-run project. However, people coming from other VCSs seem to make this a sticking point at work, so I added it anyway, if only to see how far I could stretch gitolite's config file while keeping its simplicity intact :-) ---- I'm often on #git, subject to my living in UTC+0530 time, and email is also welcome (sitaramc gmail.com is preferred, but sitaram.chamarty tcs.com may get my attention quicker). Feel free to contact me with questions or feedback. -- Sitaram [1]: http://article.gmane.org/gmane.comp.version-control.git/131834 -- Sitaram -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]

Download: http://tortoisegit.googlecode.com/files/TortoiseGit-1.3.6.0-32bit.msi http://tortoisegit.googlecode.com/files/TortoiseGit-1.3.6.0-64bit.msi = Release 1.3.6.0 = == Bug Fix == * Fixed log crash when no body message at commit * Fixed ... [More] issue #298: State of "View Patch/Hide Patch" link (commit window) is wrong in some ways * Fixed issue #301: Show Log crashes with empty repo = Release 1.3.5.0 = == Features == * Support Annotated tags Implemented issue #274: Enhancement: Annotated tags * shallow clones support --depth at clone dialog Fixed issue #290: Shallow clones support --depth at clone dialog * Improve Diff Dialog Change commit at diff dialog Diff commit context menu show in git repository * Log Dialog Direct Launch external diff when open dialog at file Log can refresh when Click Rev button. * Context menu Use setting dialog to control which menuitem is external menu. * Sync Dialog Add remote update at sync dialog == Bug Fix == * Fixed issue #294: commit template not supported and support msysgit unix path * Fixed issue #282: Fom/To/Messages/Authors/Paths filters are eventually disabled * Fixed issue #292: Very large dialog when merging * Fixed issue #291: Blame makes empty "UserImages.bmp" file * Fix crash when copy several log message to clipboards * Fixed issue #284: Show Log crashes when switching branches wait for log thread exit * Fixed issue #285: Cherry picking no longer works * Fix fetch command can't sync remote branch at sync dialog -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]

A release candidate Git 1.7.0.rc2 is available at the usual places for testing: 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) ... [More] 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) Hopefully this is the final -rc before the real thing in a few days. ---------------------------------------------------------------- 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 ammount 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'. Updates since v1.6.6 -------------------- (subsystems) * "git fast-import" updates; adds "option" and "feature" to detect the mismatch between fast-import and the frontends that produce the input stream. * "git svn" support of subversion "merge tickets" and miscellaneous fixes. * "gitk" updates. * "gitweb" updates (code clean-up, load checking etc.) (portability) * Some more MSVC portability patches for msysgit port. * Minimum Pthreads emulation for msysgit port. (performance) * More performance improvement patches for msysgit port. (usability, bells and whistles) * More commands learned "--quiet" and "--[no-]progress" options. * Various commands given by the end user (e.g. diff.type.textconv, and GIT_EDITOR) can be specified with command line arguments. E.g. it is now possible to say "[diff "utf8doc"] textconv = nkf -w". * "sparse checkout" feature allows only part of the work tree to be checked out. * HTTP transfer can use authentication scheme other than basic (i.e./e.g. digest). * Switching from a version of superproject that used to have a submodule to another version of superproject that no longer has it did not remove the submodule directory when it should (namely, when you are not interested in the submodule at all and didn't clone/checkout). * A new attribute conflict-marker-size can be used to change the size of the conflict markers from the default 7; this is useful when tracked contents (e.g. git-merge documentation) have strings that resemble the conflict markers. * A new syntax "@{upstream}" can be used on the command line to substitute the name of the "upstream" of the branch. Missing branch defaults to the current branch, so "git fetch && git merge @{upstream}" will be equivalent to "git pull". * "git branch --set-upstream" can be used to update the (surprise!) upstream i.e. where the branch is supposed to pull and merge from (or rebase onto). * "git checkout A...B" is a way to detach HEAD at the merge base between A and B. * "git checkout -m path" to reset the work tree file back into the conflicted state works even when you already ran "git add path" and resolved the conflicts. * "git commit --date=''" can be used to override the author date just like "git commit --author=' '" can be used to override the author identity. * "git commit --no-status" can be used to omit the listing of the index and the work tree status in the editor used to prepare the log message. * "git commit" warns a bit more aggressively until you configure user.email, whose default value almost always is not (and fundamentally cannot be) what you want. * "git difftool" has been extended to make it easier to integrate it with gitk. * "git fetch --all" can now be used in place of "git remote update". * "git grep" does not rely on external grep anymore. It can use more than one threads to accelerate the operation. * "git grep" learned "--quiet" option. * "git log" and friends learned "--glob=heads/*" syntax that is a more flexible way to complement "--branches/--tags/--remotes". * "git merge" learned to pass options specific to strategy-backends. E.g. - "git merge -Xsubtree=path/to/directory" can be used to tell the subtree strategy how much to shift the trees explicitly. - "git merge -Xtheirs" can be used to auto-merge as much as possible, while discarding your own changes and taking merged version in conflicted regions. * "git push" learned "git push origin --delete branch", a syntactic sugar for "git push origin :branch". * "git push" learned "git push --set-upstream origin forker:forkee" that lets you configure your "forker" branch to later pull from "forkee" branch at "origin". * "git rebase --onto A...B" means the history is replayed on top of the merge base between A and B. * "git rebase -i" learned new action "fixup", that squashes the change but does not affect existing log message. * "git rebase -i" also learned --autosquash option, that is useful together with the new "fixup" action. * "git remote" learned set-url subcommand, to update (surprise!) url for an existing remote nickname. * "git rerere" learned "forget path" subcommand. Together with "git checkout -m path" it will be useful when you recorded a wrong resolution. * Use of "git reset --merge" has become easier when resetting away a conflicted mess left in the work tree. * "git rerere" had rerere.autoupdate configuration but there was no way to countermand it from the command line; --no-rerere-autoupdate option given to "merge", "revert", etc. fixes this. * "git status" learned "-s(hort)" output format. (developers) * The infrastructure to build foreign SCM interface has been updated. * Many more commands are now built-in. * THREADED_DELTA_SEARCH is no more. If you build with threads, delta compression will always take advantage of it. Fixes since v1.6.6 ------------------ All of the fixes in v1.6.6.X maintenance series are included in this release, unless otherwise noted. * "git branch -d branch" used to refuse deleting the branch even when the branch is fully merged to its upstream branch if it is not merged to the current branch. It now deletes it in such a case. * "git config -f " run from a subdirectory misbehaved. 65807ee (builtin-config: Fix crash when using "-f " from non-root dir, 2010-01-26) may be merged to older maintenance branches. * "git fast-import" did not correctly handle large blobs that may bust the pack size limit. * When using "git status" or asking "git diff" to compare the work tree with something, they used to consider that a checked-out submodule with uncommitted changes is not modified; this could cause people to forget committing these changes in the submodule before committing in the superproject. They now consider such a change as a modification and "git diff" will append a "-dirty" to the work tree side when generating patch output or when used with the --submodule option. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]

Hi all, git-subtree is an alternative to git submodules. It makes it easier to use git's "subtree" merge strategy, and also provides a "split" operation to do the opposite (extracting a subtree back into the parent project) so you can go back and ... [More] forth. It's been awhile since I made an actual official release, so I just tagged v0.3. You can find it at http://github.com/apenwarr/git-subtree. Main changes in this version: - a new 'git subtree pull' command to complement 'git subtree merge' - improvements to docs and license notices - various bugfixes. Jakub Suder has also written a new tutorial on how to use git-subtree: http://psionides.jogger.pl/2010/02/04/sharing-code-between-projects-with-git-subtree/ git-subtree appears to be gaining in popularity (it how has 94 followers on github, and people are obviously using it enough to submit patches). Thoughts about whether (and how) to submit it for inclusion into core git are welcome. Amiel Martin (2): fixed order of assertion in tests sort assertion to make it more generic Arlen Cuss (1): Fix refspecs in given example for git subtree pull. Avery Pennarun (13): Docs: when pushing to github, the repo path needs to end in .git Improve patch to use git --exec-path: add to PATH instead. Fix behaviour if you have a branch named the same as your --prefix Add a README that says to email me instead of using github mail. Merge branch 'master' of git://github.com/voxpelli/git-subtree If someone provides a --prefix that ends with slash, strip the slash. Fix a minor problem in identifying squashes vs. normal splits. cmd_pull didn't support --squash correctly. Add some tips for how to install. Oops, forgot a COPYING file. It's GPLv2. Weird, I forgot to have 'make test' call test.sh. Merge branch 'master' of git://github.com/psionides/git-subtree Jakub's changes broke the progress message slightly. Ben Walton (2): add installation support to Makefile make git version dynamic when building documentation Jakub Suder (9): added -p alias for --prefix added -m/--message option for setting merge commit message allow using --branch with existing branches if it makes sense fix for subtree split not finding proper base for new commits changed alias for --prefix from -p to -P fixed bug in commit message for split added tests for recent changes added temporary test dirs to gitignore improved rev_is_descendant_of_branch() function Pelle Wessman (1): Check that the type of the tree really is a tree and not a commit kTln2 (1): Add explicit path of git installation by 'git --exec-path'. Have fun, Avery -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]

A release candidate Git 1.7.0.rc1 is available at the usual places for testing: http://www.kernel.org/pub/software/scm/git/ git-1.7.0.rc1.tar.{gz,bz2} (source tarball) git-htmldocs-1.7.0.rc1.tar.{gz,bz2} (preformatted docs) ... [More] git-manpages-1.7.0.rc1.tar.{gz,bz2} (preformatted docs) The RPM binary packages for a few architectures are found in: testing/git-*-1.7.0.rc1-1.fc11.$arch.rpm (RPM) 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 pathspec. * "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 ammount 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. Updates since v1.6.6 -------------------- (subsystems) * "git fast-import" updates; adds "option" and "feature" to detect the mismatch between fast-import and the frontends that produce the input stream. * "git svn" support of subversion "merge tickets" and miscellaneous fixes. * "gitk" updates. (portability) * Some more MSVC portability patches for msysgit port. * Minimum Pthreads emulation for msysgit port. (performance) * More performance improvement patches for msysgit port. (usability, bells and whistles) * More commands learned "--quiet" and "--[no-]progress" options. * Various commands given by the end user (e.g. diff.type.textconv, and GIT_EDITOR) can be specified with command line arguments. E.g. it is now possible to say "[diff "utf8doc"] textconv = nkf -w". * "sparse checkout" feature allows only part of the work tree to be checked out. * HTTP transfer can use authentication scheme other than basic (i.e./e.g. digest). * Switching from a version of superproject that used to have a submodule to another version of superproject that no longer has it did not remove the submodule directory when it should (namely, when you are not interested in the submodule at all and didn't clone/checkout). * A new attribute conflict-marker-size can be used to change the size of the conflict markers from the default 7; this is useful when tracked contents (e.g. git-merge documentation) have strings that resemble the conflict markers. * A new syntax "@{upstream}" can be used on the command line to substitute the name of the "upstream" of the branch. Missing branch defaults to the current branch, so "git fetch && git merge @{upstream}" will be equivalent to "git pull". * "git branch --set-upstream" can be used to update the (surprise!) upstream i.e. where the branch is supposed to pull and merge from (or rebase onto). * "git checkout A...B" is a way to detach HEAD at the merge base between A and B. * "git checkout -m path" to reset the work tree file back into the conflicted state works even when you already ran "git add path" and resolved the conflicts. * "git commit --date=''" can be used to override the author date just like "git commit --author=' '" can be used to override the author identity. * "git commit --no-status" can be used to omit the listing of the index and the work tree status in the editor used to prepare the log message. * "git commit" warns a bit more aggressively until you configure user.email, whose default value almost always is not (and fundamentally cannot be) what you want. * "git difftool" has been extended to make it easier to integrate it with gitk. * "git fetch --all" can now be used in place of "git remote update". * "git grep" does not rely on external grep anymore. It can use more than one threads to accelerate the operation. * "git grep" learned "--no-index" option, to search inside contents that are not managed by git. * "git grep" learned "--quiet" option. * "git log" and friends learned "--glob=heads/*" syntax that is a more flexible way to complement "--branches/--tags/--remotes". * "git merge" learned to pass options specific to strategy-backends. E.g. - "git merge -Xsubtree=path/to/directory" can be used to tell the subtree strategy how much to shift the trees explicitly. - "git merge -Xtheirs" can be used to auto-merge as much as possible, while discarding your own changes and taking merged version in conflicted regions. * "git push" learned "git push origin --delete branch", a syntactic sugar for "git push origin :branch". * "git push" learned "git push --set-upstream origin forker:forkee" that lets you configure your "forker" branch to later pull from "forkee" branch at "origin". * "git rebase --onto A...B" means the history is replayed on top of the merge base between A and B. * "git rebase -i" learned new action "fixup", that squashes the change but does not affect existing log message. * "git rebase -i" also learned --autosquash option, that is useful together with the new "fixup" action. * "git remote" learned set-url subcommand, to update (surprise!) url for an existing remote nickname. * "git rerere" learned "forget path" subcommand. Together with "git checkout -m path" it will be useful when you recorded a wrong resolution. * Use of "git reset --merge" has become easier when resetting away a conflicted mess left in the work tree. * "git rerere" had rerere.autoupdate configuration but there was no way to countermand it from the command line; --no-rerere-autoupdate option given to "merge", "revert", etc. fixes this. * "git status" learned "-s(hort)" output format. (developers) * The infrastructure to build foreign SCM interface has been updated. * Many more commands are now built-in. Fixes since v1.6.6 ------------------ All of the fixes in v1.6.6.X maintenance series are included in this release, unless otherwise noted. * "git branch -d branch" used to refuse deleting the branch even when the branch is fully merged to its upstream branch if it is not merged to the current branch. It now deletes it in such a case. * "git config -f " run from a subdirectory misbehaved. 65807ee (builtin-config: Fix crash when using "-f " from non-root dir, 2010-01-26) may be merged to older maintenance branches. * When "git diff" is asked to compare the work tree with something, it used to consider that a checked-out submodule with uncommitted changes is not modified; this could cause people to forget committing these changes in the submodule before committing in the superproject. It now considers such a change as a modification. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]

Download: http://tortoisegit.googlecode.com/files/TortoiseGit-1.3.2.0-32bit.msi http://tortoisegit.googlecode.com/files/TortoiseGit-1.3.2.0-64bit.msi This release build Git source as a DLL. LogDialog will call gitdll to fetch log instead of capture ... [More] git.exe output. Improve refresh and all branch user experience. refresh can abort runing fetch log commit. KNOWN ISSUE: gitdll.dll will miss if install on the 1.2.1.0 or previous version. work around: Remove previous version before install 1.3.2.0, or launch 1.3.2.0 setup and repair it. I am sorry for this issue. = Release 1.3.2.0 = == Bug Fix == * Fixed issue #276: Crash on seeing diff with previous version * Fixed issue #275: Load gitweb for 'Browse' button * Fixed issue #265: Log dialog: Date picker throws multiple error messages when date is before 1.1.1970 * Fix RefLogDlg crash = Release 1.3.1.0 = == Features == * Improve Log Dialog. Speed up log fetch speed. Build Git source as a DLL. LogDialog will call gitdll to fetch log instead of capture git.exe output. Improve refresh and all branch user experience. refresh can abort runing fetch log commit. * Improve icon-overlay Give up igit.exe and use tgit which build from git source by VS. use tgit.exe statusex to get file status. Don't list all untracked files. * Improve commit and checkout modify dialog Don't show file that is only time stamp change and no context change. Run git-update-index first when open commit and checkout out modify dialog. == Bug Fix == * Fixed issue #234: First log(first commit in history) was missing... * Fixed issue #232: "No Commit" Option always acitve * Fix Issue 236: CGit::GetRemoteList uses bad regular expression * Fix blame show wrong when first char is '^' * Workaround show "fail" even git run success at sometime by remove "fail" message. * Issue 265: Log dialog: Date picker throws multiple error messages when date is before 1.1.1970 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]

The latest maintenance release Git 1.6.6.1 is available at the usual places: http://www.kernel.org/pub/software/scm/git/ git-1.6.6.1.tar.{gz,bz2} (source tarball) git-htmldocs-1.6.6.1.tar.{gz,bz2} (preformatted docs) ... [More] git-manpages-1.6.6.1.tar.{gz,bz2} (preformatted docs) The RPM binary packages for a few architectures are found in: RPMS/$arch/git-*-1.6.6.1-1.fc11.$arch.rpm (RPM) Git v1.6.6.1 Release Notes ========================== Fixes since v1.6.6 ------------------ * "git blame" did not work well when commit lacked the author name. * "git branch -a name" wasn't diagnosed as an error. * "git count-objects" did not handle packfiles that are bigger than 4G on platforms with 32-bit off_t. * "git checkout -m other" while on a branch that does not have any commit segfaulted, instead of failing. * "git fast-import" choked when fed a tag that do not point at a commit. * "git grep" finding from work tree files could have fed garbage to the underlying regexec(3). * "git grep -L" didn't show empty files (they should never match, and they should always appear in -L output as unmatching). * "git rebase -i" did not abort cleanly if it failed to launch the editor. * "git reset --hard" did not work correctly when GIT_WORK_TREE environment variable is used to point at the root of the true work tree. * http-backend was not listed in the command list in the documentation. * Building on FreeBSD (both 7 and 8) needs OLD_ICONV set in the Makefile * "git checkout -m some-branch" while on an unborn branch crashed. Other minor documentation updates are included. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]

An maintenance release Git 1.6.5.8 is available at the usual places: http://www.kernel.org/pub/software/scm/git/ git-1.6.5.8.tar.{gz,bz2} (source tarball) git-htmldocs-1.6.5.8.tar.{gz,bz2} (preformatted docs) ... [More] git-manpages-1.6.5.8.tar.{gz,bz2} (preformatted docs) The RPM binary packages for a few architectures are found in: RPMS/$arch/git-*-1.6.5.8-1.fc11.$arch.rpm (RPM) Git v1.6.5.8 Release Notes ========================== Fixes since v1.6.5.7 -------------------- * "git count-objects" did not handle packfiles that are bigger than 4G on platforms with 32-bit off_t. * "git rebase -i" did not abort cleanly if it failed to launch the editor. * "git blame" did not work well when commit lacked the author name. * "git fast-import" choked when handling a tag that points at an object that is not a commit. * "git reset --hard" did not work correctly when GIT_WORK_TREE environment variable is used to point at the root of the true work tree. * "git grep" fed a buffer that is not NUL-terminated to underlying regexec(). * "git checkout -m other" while on a branch that does not have any commit segfaulted, instead of failing. * "git branch -a other" should have diagnosed the command as an error. Other minor documentation updates are also included. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]