kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/scmgit-docs/PLIST

155 lines
3.7 KiB
Text
Raw Normal View History

Changes 1.7.3.2: This is primarily to push out many documentation fixes accumulated since the 1.7.3.1 release. Changes 1.7.3.1: * "git stash show stash@{$n}" was accidentally broken in 1.7.3 ("git stash show" without any argument still worked, though). * "git stash branch $branch stash@{$n}" was accidentally broken in 1.7.3 and started dropping the named stash even when branch creation failed. Changes 1.7.3: * git-gui, now at version 0.13.0, got various updates and a new maintainer, Pat Thoyts. * Gitweb allows its configuration to change per each request; it used to read the configuration once upon startup. * When git finds a corrupt object, it now reports the file that contains it. * "git checkout -B <it>" is a shorter way to say "git branch -f <it>" followed by "git checkout <it>". * When "git checkout" or "git merge" refuse to proceed in order to protect local modification to your working tree, they used to stop after showing just one path that might be lost. They now show all, in a format that is easier to read. * "git clean" learned "-e" ("--exclude") option. * Hunk headers produced for C# files by "git diff" and friends show more relevant context than before. * diff.ignoresubmodules configuration variable can be used to squelch the differences in submodules reported when running commands (e.g. "diff", "status", etc.) at the superproject level. * http.useragent configuration can be used to lie who you are to your restrictive firewall. * "git rebase --strategy <s>" learned "-X" option to pass extra options that are understood by the chosen merge strategy. * "git rebase -i" learned "exec" that you can insert into the insn sheet to run a command between its steps. * "git rebase" between branches that have many binary changes that do not conflict should be faster. * "git rebase -i" peeks into rebase.autosquash configuration and acts as if you gave --autosquash from the command line.
2010-10-28 12:23:07 +02:00
@comment $NetBSD: PLIST,v 1.8 2010/10/28 10:23:08 adam Exp $
Switch GIT to use a meta-pkg hierarchy like, for example, devel/subversion. Also, update to 1.5.3.7. Fixes since v1.5.3.6 -------------------- * git-send-email added 8-bit contents to the payload without marking it as 8-bit in a CTE header. * "git-bundle create a.bndl HEAD" dereferenced the symref and did not record the ref as 'HEAD'; this prevented a bundle from being used as a normal source of git-clone. * The code to reject nonsense command line of the form "git-commit -a paths..." and "git-commit --interactive paths..." were broken. * Adding a signature that is not ASCII-only to an original commit that is ASCII-only would make the result non-ASCII. "git-format-patch -s" did not mark such a message correctly with MIME encoding header. * git-add sometimes did not mark the resulting index entry stat-clean. This affected only cases when adding the contents with the same length as the previously staged contents, and the previous staging made the index entry "racily clean". * git-commit did not honor GIT_INDEX_FILE the user had in the environment. * When checking out a revision, git-checkout did not report where the updated HEAD is if you happened to have a file called HEAD in the work tree. * "git-rev-list --objects" mishandled a tree that points at a submodule. * "git cvsimport" was not ready for packed refs that "git gc" can produce and gave incorrect results. * Many scripted Porcelains were confused when you happened to have a file called "HEAD" in your work tree. * Miscellaneous updates to the user manual and documentation.
2007-12-12 05:22:20 +01:00
man/man1/git-add.1
man/man1/git-am.1
man/man1/git-annotate.1
man/man1/git-apply.1
man/man1/git-archimport.1
man/man1/git-archive.1
man/man1/git-bisect.1
man/man1/git-blame.1
man/man1/git-branch.1
man/man1/git-bundle.1
man/man1/git-cat-file.1
man/man1/git-check-attr.1
man/man1/git-check-ref-format.1
man/man1/git-checkout-index.1
man/man1/git-checkout.1
man/man1/git-cherry-pick.1
man/man1/git-cherry.1
man/man1/git-citool.1
man/man1/git-clean.1
man/man1/git-clone.1
man/man1/git-commit-tree.1
man/man1/git-commit.1
man/man1/git-config.1
man/man1/git-count-objects.1
man/man1/git-cvsexportcommit.1
man/man1/git-cvsimport.1
man/man1/git-cvsserver.1
man/man1/git-daemon.1
man/man1/git-describe.1
man/man1/git-diff-files.1
man/man1/git-diff-index.1
man/man1/git-diff-tree.1
man/man1/git-diff.1
Update scmgit to 1.6.3.3. This version fixes the remote DoS problem in http://secunia.com/advisories/35437/. Major changes between 1.6.2 and 1.6.3: * various git-svn updates. * git-gui updates, including an update to Russian translation, and a fix to an infinite loop when showing an empty diff. * gitk updates, including an update to Russian translation and improved Windows support. * many uses of lstat(2) in the codepath for "git checkout" have been optimized out. * usuability improvements. * bug fixes.
2009-07-19 03:29:32 +02:00
man/man1/git-difftool.1
Update to git-1.5.4. Remove stray Makefile.common in scmgit-docs. There are quite a few changes and (welcomed) fixes: please see the release notes in ${WRKSRC}/Documentation/RelNotes-1.5.4. A small subset of the changes are included here. Added ----- * i18n support for gitk. Removal ------- * "git svnimport" was removed in favor of "git svn". It is still there in the source tree (contrib/examples) but unsupported. * As git-commit and git-status have been rewritten, "git runstatus" helper script lost all its users and has been removed. Fixes since v1.5.3 (unique to the 1.5.4 branch) ------------------ These fixes are only in v1.5.4 and not backported to v1.5.3 maintenance series. * The way "git diff --check" behaves is much more consistent with the way "git apply --whitespace=warn" works. * "git svn" talking with the SVN over HTTP will correctly quote branch and project names. * "git config" did not work correctly on platforms that define REG_NOMATCH to an even number. * Recent versions of AsciiDoc 8 has a change to break our documentation; a workaround has been implemented. * "git diff --color-words" colored context lines in a wrong color.
2008-02-06 08:53:31 +01:00
man/man1/git-fast-export.1
Switch GIT to use a meta-pkg hierarchy like, for example, devel/subversion. Also, update to 1.5.3.7. Fixes since v1.5.3.6 -------------------- * git-send-email added 8-bit contents to the payload without marking it as 8-bit in a CTE header. * "git-bundle create a.bndl HEAD" dereferenced the symref and did not record the ref as 'HEAD'; this prevented a bundle from being used as a normal source of git-clone. * The code to reject nonsense command line of the form "git-commit -a paths..." and "git-commit --interactive paths..." were broken. * Adding a signature that is not ASCII-only to an original commit that is ASCII-only would make the result non-ASCII. "git-format-patch -s" did not mark such a message correctly with MIME encoding header. * git-add sometimes did not mark the resulting index entry stat-clean. This affected only cases when adding the contents with the same length as the previously staged contents, and the previous staging made the index entry "racily clean". * git-commit did not honor GIT_INDEX_FILE the user had in the environment. * When checking out a revision, git-checkout did not report where the updated HEAD is if you happened to have a file called HEAD in the work tree. * "git-rev-list --objects" mishandled a tree that points at a submodule. * "git cvsimport" was not ready for packed refs that "git gc" can produce and gave incorrect results. * Many scripted Porcelains were confused when you happened to have a file called "HEAD" in your work tree. * Miscellaneous updates to the user manual and documentation.
2007-12-12 05:22:20 +01:00
man/man1/git-fast-import.1
man/man1/git-fetch-pack.1
man/man1/git-fetch.1
man/man1/git-filter-branch.1
man/man1/git-fmt-merge-msg.1
man/man1/git-for-each-ref.1
man/man1/git-format-patch.1
man/man1/git-fsck-objects.1
man/man1/git-fsck.1
man/man1/git-gc.1
man/man1/git-get-tar-commit-id.1
man/man1/git-grep.1
man/man1/git-gui.1
man/man1/git-hash-object.1
Update to git-1.5.4. Remove stray Makefile.common in scmgit-docs. There are quite a few changes and (welcomed) fixes: please see the release notes in ${WRKSRC}/Documentation/RelNotes-1.5.4. A small subset of the changes are included here. Added ----- * i18n support for gitk. Removal ------- * "git svnimport" was removed in favor of "git svn". It is still there in the source tree (contrib/examples) but unsupported. * As git-commit and git-status have been rewritten, "git runstatus" helper script lost all its users and has been removed. Fixes since v1.5.3 (unique to the 1.5.4 branch) ------------------ These fixes are only in v1.5.4 and not backported to v1.5.3 maintenance series. * The way "git diff --check" behaves is much more consistent with the way "git apply --whitespace=warn" works. * "git svn" talking with the SVN over HTTP will correctly quote branch and project names. * "git config" did not work correctly on platforms that define REG_NOMATCH to an even number. * Recent versions of AsciiDoc 8 has a change to break our documentation; a workaround has been implemented. * "git diff --color-words" colored context lines in a wrong color.
2008-02-06 08:53:31 +01:00
man/man1/git-help.1
Update to 1.6.6, requested by agc. Git v1.6.6 Release Notes ======================== Notes on behaviour change ------------------------- * In this release, "git fsck" defaults to "git fsck --full" and checks packfiles, and because of this it will take much longer to complete than before. If you prefer a quicker check only on loose objects (the old default), you can say "git fsck --no-full". This has been supported by 1.5.4 and newer versions of git, so it is safe to write it in your script even if you use slightly older git on some of your machines. Preparing yourselves for compatibility issues in 1.7.0 ------------------------------------------------------ In git 1.7.0, which is planned to be the release after 1.6.6, there will be a handful of behaviour changes that will break backward compatibility. These changes were discussed long time ago and existing behaviours have been identified as more problematic to the userbase than keeping them for the sake of backward compatibility. When necessary, a transition strategy for existing users has been designed not to force them running around setting configuration variables and updating their scripts in order to either keep the traditional behaviour or adjust to the new behaviour, on the day their sysadmin decides to install the new version of git. When we switched from "git-foo" to "git foo" in 1.6.0, even though the change had been advertised and the transition guide had been provided for a very long time, the users procrastinated during the entire transtion period, and ended up panicking on the day their sysadmins updated their git installation. We are trying to avoid repeating that unpleasantness in the 1.7.0 release. For changes decided to be in 1.7.0, commands that will be affected have been much louder to strongly discourage such procrastination, and they continue to be in this release. If you have been using recent versions of git, you would have seen warnings issued when you used features whose behaviour will change, with a clear instruction on how to keep the existing behaviour if you want to. You hopefully are already well prepared. Of course, we have also been giving "this and that will change in 1.7.0; prepare yourselves" warnings in the release notes and announcement messages for the past few releases. Let's see how well users will fare this time. * "git push" into a branch that is currently checked out (i.e. pointed by HEAD in a repository that is not bare) will be 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. Versions of git since 1.6.2 have issued a loud warning when you tried to do these operations without setting the configuration, so repositories of people who still need to be able to perform such a push should already have been future proofed. 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 process that already took place so far. * "git send-email" will 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. Git 1.6.6 (this release) will issue a warning about the upcoming default change, when it uses the traditional "deep threading" behaviour as the built-in default. To squelch the warning but still use the "deep threading" behaviour, give --chain-reply-to option or set sendemail.chainreplyto to true. It has been possible to configure send-email to send "shallow thread" by setting sendemail.chainreplyto configuration variable to false. The only thing 1.7.0 release will do is to change the default when you haven't configured that variable. * "git status" will not be "git commit --dry-run". This change does not affect you if you run the command without pathspec. Nobody sane found the current behaviour of "git status Makefile" useful nor meaningful, and it confused users. "git commit --dry-run" has been provided as a way to get the current behaviour of this command since 1.6.5. * "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 1.7.0, the "ignore whitespaces" will affect the semantics of the diff operation itself. A change that does not affect anything but whitespaces will be reported with zero exit status when run with --exit-code, and there will not be "diff --git" header for such a change. Updates since v1.6.5 -------------------- (subsystems) * various gitk updates including use of themed widgets under Tk 8.5, Japanese translation, a fix to a bug when running "gui blame" from a subdirectory, etc. * various git-gui updates including new translations, wm states fixes, Tk bug workaround after quitting, improved heuristics to trigger gc, etc. * various git-svn updates. * "git fetch" over http learned a new mode that is different from the traditional "dumb commit walker". (portability) * imap-send can be built on mingw port. (performance) * "git diff -B" has smaller memory footprint. (usability, bells and whistles) * The object replace mechanism can be bypassed with --no-replace-objects global option given to the "git" program. * In configuration files, a few variables that name paths can begin with ~/ and ~username/ and they are expanded as expected. * "git subcmd -h" now shows short usage help for many more subcommands. * "git bisect reset" can reset to an arbitrary commit. * "git checkout frotz" when there is no local branch "frotz" but there is only one remote tracking branch "frotz" is taken as a request to start the named branch at the corresponding remote tracking branch. * "git commit -c/-C/--amend" can be told with a new "--reset-author" option to ignore authorship information in the commit it is taking the message from. * "git describe" can be told to add "-dirty" suffix with "--dirty" option. * "git diff" learned --submodule option to show a list of one-line logs instead of differences between the commit object names. * "git diff" learned to honor diff.color.func configuration to paint function name hint printed on the hunk header "@@ -j,k +l,m @@" line in the specified color. * "git fetch" learned --all and --multiple options, to run fetch from many repositories, and --prune option to remove remote tracking branches that went stale. These make "git remote update" and "git remote prune" less necessary (there is no plan to remove "remote update" nor "remote prune", though). * "git fsck" by default checks the packfiles (i.e. "--full" is the default); you can turn it off with "git fsck --no-full". * "git grep" can use -F (fixed strings) and -i (ignore case) together. * import-tars contributed fast-import frontend learned more types of compressed tarballs. * "git instaweb" knows how to talk with mod_cgid to apache2. * "git log --decorate" shows the location of HEAD as well. * "git log" and "git rev-list" learned to take revs and pathspecs from the standard input with the new "--stdin" option. * "--pretty=format" option to "log" family of commands learned: . to wrap text with the "%w()" specifier. . to show reflog information with "%g[sdD]" specifier. * "git notes" command to annotate existing commits. * "git merge" (and "git pull") learned --ff-only option to make it fail if the merge does not result in a fast-forward. * "git mergetool" learned to use p4merge. * "git rebase -i" learned "reword" that acts like "edit" but immediately starts an editor to tweak the log message without returning control to the shell, which is done by "edit" to give an opportunity to tweak the contents. * "git send-email" can be told with "--envelope-sender=auto" to use the same address as "From:" address as the envelope sender address. * "git send-email" will issue a warning when it defaults to the --chain-reply-to behaviour without being told by the user and instructs to prepare for the change of the default in 1.7.0 release. * In "git submodule add <repository> <path>", <path> is now optional and inferred from <repository> the same way "git clone <repository>" does. * "git svn" learned to read SVN 1.5+ and SVK merge tickets. * "git svn" learned to recreate empty directories tracked only by SVN. * "gitweb" can optionally render its "blame" output incrementally (this requires JavaScript on the client side). * Author names shown in gitweb output are links to search commits by the author. Fixes since v1.6.5 ------------------ All of the fixes in v1.6.5.X maintenance series are included in this release, unless otherwise noted. 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.
2010-01-15 11:36:41 +01:00
man/man1/git-http-backend.1
Switch GIT to use a meta-pkg hierarchy like, for example, devel/subversion. Also, update to 1.5.3.7. Fixes since v1.5.3.6 -------------------- * git-send-email added 8-bit contents to the payload without marking it as 8-bit in a CTE header. * "git-bundle create a.bndl HEAD" dereferenced the symref and did not record the ref as 'HEAD'; this prevented a bundle from being used as a normal source of git-clone. * The code to reject nonsense command line of the form "git-commit -a paths..." and "git-commit --interactive paths..." were broken. * Adding a signature that is not ASCII-only to an original commit that is ASCII-only would make the result non-ASCII. "git-format-patch -s" did not mark such a message correctly with MIME encoding header. * git-add sometimes did not mark the resulting index entry stat-clean. This affected only cases when adding the contents with the same length as the previously staged contents, and the previous staging made the index entry "racily clean". * git-commit did not honor GIT_INDEX_FILE the user had in the environment. * When checking out a revision, git-checkout did not report where the updated HEAD is if you happened to have a file called HEAD in the work tree. * "git-rev-list --objects" mishandled a tree that points at a submodule. * "git cvsimport" was not ready for packed refs that "git gc" can produce and gave incorrect results. * Many scripted Porcelains were confused when you happened to have a file called "HEAD" in your work tree. * Miscellaneous updates to the user manual and documentation.
2007-12-12 05:22:20 +01:00
man/man1/git-http-fetch.1
man/man1/git-http-push.1
man/man1/git-imap-send.1
man/man1/git-index-pack.1
man/man1/git-init-db.1
man/man1/git-init.1
man/man1/git-instaweb.1
man/man1/git-log.1
man/man1/git-lost-found.1
man/man1/git-ls-files.1
man/man1/git-ls-remote.1
man/man1/git-ls-tree.1
man/man1/git-mailinfo.1
man/man1/git-mailsplit.1
man/man1/git-merge-base.1
man/man1/git-merge-file.1
man/man1/git-merge-index.1
man/man1/git-merge-one-file.1
man/man1/git-merge-tree.1
man/man1/git-merge.1
Update scmgit to 1.6.3.3. This version fixes the remote DoS problem in http://secunia.com/advisories/35437/. Major changes between 1.6.2 and 1.6.3: * various git-svn updates. * git-gui updates, including an update to Russian translation, and a fix to an infinite loop when showing an empty diff. * gitk updates, including an update to Russian translation and improved Windows support. * many uses of lstat(2) in the codepath for "git checkout" have been optimized out. * usuability improvements. * bug fixes.
2009-07-19 03:29:32 +02:00
man/man1/git-mergetool--lib.1
Update to 1.6.6, requested by agc. Git v1.6.6 Release Notes ======================== Notes on behaviour change ------------------------- * In this release, "git fsck" defaults to "git fsck --full" and checks packfiles, and because of this it will take much longer to complete than before. If you prefer a quicker check only on loose objects (the old default), you can say "git fsck --no-full". This has been supported by 1.5.4 and newer versions of git, so it is safe to write it in your script even if you use slightly older git on some of your machines. Preparing yourselves for compatibility issues in 1.7.0 ------------------------------------------------------ In git 1.7.0, which is planned to be the release after 1.6.6, there will be a handful of behaviour changes that will break backward compatibility. These changes were discussed long time ago and existing behaviours have been identified as more problematic to the userbase than keeping them for the sake of backward compatibility. When necessary, a transition strategy for existing users has been designed not to force them running around setting configuration variables and updating their scripts in order to either keep the traditional behaviour or adjust to the new behaviour, on the day their sysadmin decides to install the new version of git. When we switched from "git-foo" to "git foo" in 1.6.0, even though the change had been advertised and the transition guide had been provided for a very long time, the users procrastinated during the entire transtion period, and ended up panicking on the day their sysadmins updated their git installation. We are trying to avoid repeating that unpleasantness in the 1.7.0 release. For changes decided to be in 1.7.0, commands that will be affected have been much louder to strongly discourage such procrastination, and they continue to be in this release. If you have been using recent versions of git, you would have seen warnings issued when you used features whose behaviour will change, with a clear instruction on how to keep the existing behaviour if you want to. You hopefully are already well prepared. Of course, we have also been giving "this and that will change in 1.7.0; prepare yourselves" warnings in the release notes and announcement messages for the past few releases. Let's see how well users will fare this time. * "git push" into a branch that is currently checked out (i.e. pointed by HEAD in a repository that is not bare) will be 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. Versions of git since 1.6.2 have issued a loud warning when you tried to do these operations without setting the configuration, so repositories of people who still need to be able to perform such a push should already have been future proofed. 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 process that already took place so far. * "git send-email" will 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. Git 1.6.6 (this release) will issue a warning about the upcoming default change, when it uses the traditional "deep threading" behaviour as the built-in default. To squelch the warning but still use the "deep threading" behaviour, give --chain-reply-to option or set sendemail.chainreplyto to true. It has been possible to configure send-email to send "shallow thread" by setting sendemail.chainreplyto configuration variable to false. The only thing 1.7.0 release will do is to change the default when you haven't configured that variable. * "git status" will not be "git commit --dry-run". This change does not affect you if you run the command without pathspec. Nobody sane found the current behaviour of "git status Makefile" useful nor meaningful, and it confused users. "git commit --dry-run" has been provided as a way to get the current behaviour of this command since 1.6.5. * "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 1.7.0, the "ignore whitespaces" will affect the semantics of the diff operation itself. A change that does not affect anything but whitespaces will be reported with zero exit status when run with --exit-code, and there will not be "diff --git" header for such a change. Updates since v1.6.5 -------------------- (subsystems) * various gitk updates including use of themed widgets under Tk 8.5, Japanese translation, a fix to a bug when running "gui blame" from a subdirectory, etc. * various git-gui updates including new translations, wm states fixes, Tk bug workaround after quitting, improved heuristics to trigger gc, etc. * various git-svn updates. * "git fetch" over http learned a new mode that is different from the traditional "dumb commit walker". (portability) * imap-send can be built on mingw port. (performance) * "git diff -B" has smaller memory footprint. (usability, bells and whistles) * The object replace mechanism can be bypassed with --no-replace-objects global option given to the "git" program. * In configuration files, a few variables that name paths can begin with ~/ and ~username/ and they are expanded as expected. * "git subcmd -h" now shows short usage help for many more subcommands. * "git bisect reset" can reset to an arbitrary commit. * "git checkout frotz" when there is no local branch "frotz" but there is only one remote tracking branch "frotz" is taken as a request to start the named branch at the corresponding remote tracking branch. * "git commit -c/-C/--amend" can be told with a new "--reset-author" option to ignore authorship information in the commit it is taking the message from. * "git describe" can be told to add "-dirty" suffix with "--dirty" option. * "git diff" learned --submodule option to show a list of one-line logs instead of differences between the commit object names. * "git diff" learned to honor diff.color.func configuration to paint function name hint printed on the hunk header "@@ -j,k +l,m @@" line in the specified color. * "git fetch" learned --all and --multiple options, to run fetch from many repositories, and --prune option to remove remote tracking branches that went stale. These make "git remote update" and "git remote prune" less necessary (there is no plan to remove "remote update" nor "remote prune", though). * "git fsck" by default checks the packfiles (i.e. "--full" is the default); you can turn it off with "git fsck --no-full". * "git grep" can use -F (fixed strings) and -i (ignore case) together. * import-tars contributed fast-import frontend learned more types of compressed tarballs. * "git instaweb" knows how to talk with mod_cgid to apache2. * "git log --decorate" shows the location of HEAD as well. * "git log" and "git rev-list" learned to take revs and pathspecs from the standard input with the new "--stdin" option. * "--pretty=format" option to "log" family of commands learned: . to wrap text with the "%w()" specifier. . to show reflog information with "%g[sdD]" specifier. * "git notes" command to annotate existing commits. * "git merge" (and "git pull") learned --ff-only option to make it fail if the merge does not result in a fast-forward. * "git mergetool" learned to use p4merge. * "git rebase -i" learned "reword" that acts like "edit" but immediately starts an editor to tweak the log message without returning control to the shell, which is done by "edit" to give an opportunity to tweak the contents. * "git send-email" can be told with "--envelope-sender=auto" to use the same address as "From:" address as the envelope sender address. * "git send-email" will issue a warning when it defaults to the --chain-reply-to behaviour without being told by the user and instructs to prepare for the change of the default in 1.7.0 release. * In "git submodule add <repository> <path>", <path> is now optional and inferred from <repository> the same way "git clone <repository>" does. * "git svn" learned to read SVN 1.5+ and SVK merge tickets. * "git svn" learned to recreate empty directories tracked only by SVN. * "gitweb" can optionally render its "blame" output incrementally (this requires JavaScript on the client side). * Author names shown in gitweb output are links to search commits by the author. Fixes since v1.6.5 ------------------ All of the fixes in v1.6.5.X maintenance series are included in this release, unless otherwise noted. 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.
2010-01-15 11:36:41 +01:00
man/man1/git-mergetool.1
Switch GIT to use a meta-pkg hierarchy like, for example, devel/subversion. Also, update to 1.5.3.7. Fixes since v1.5.3.6 -------------------- * git-send-email added 8-bit contents to the payload without marking it as 8-bit in a CTE header. * "git-bundle create a.bndl HEAD" dereferenced the symref and did not record the ref as 'HEAD'; this prevented a bundle from being used as a normal source of git-clone. * The code to reject nonsense command line of the form "git-commit -a paths..." and "git-commit --interactive paths..." were broken. * Adding a signature that is not ASCII-only to an original commit that is ASCII-only would make the result non-ASCII. "git-format-patch -s" did not mark such a message correctly with MIME encoding header. * git-add sometimes did not mark the resulting index entry stat-clean. This affected only cases when adding the contents with the same length as the previously staged contents, and the previous staging made the index entry "racily clean". * git-commit did not honor GIT_INDEX_FILE the user had in the environment. * When checking out a revision, git-checkout did not report where the updated HEAD is if you happened to have a file called HEAD in the work tree. * "git-rev-list --objects" mishandled a tree that points at a submodule. * "git cvsimport" was not ready for packed refs that "git gc" can produce and gave incorrect results. * Many scripted Porcelains were confused when you happened to have a file called "HEAD" in your work tree. * Miscellaneous updates to the user manual and documentation.
2007-12-12 05:22:20 +01:00
man/man1/git-mktag.1
man/man1/git-mktree.1
man/man1/git-mv.1
man/man1/git-name-rev.1
Update to 1.6.6, requested by agc. Git v1.6.6 Release Notes ======================== Notes on behaviour change ------------------------- * In this release, "git fsck" defaults to "git fsck --full" and checks packfiles, and because of this it will take much longer to complete than before. If you prefer a quicker check only on loose objects (the old default), you can say "git fsck --no-full". This has been supported by 1.5.4 and newer versions of git, so it is safe to write it in your script even if you use slightly older git on some of your machines. Preparing yourselves for compatibility issues in 1.7.0 ------------------------------------------------------ In git 1.7.0, which is planned to be the release after 1.6.6, there will be a handful of behaviour changes that will break backward compatibility. These changes were discussed long time ago and existing behaviours have been identified as more problematic to the userbase than keeping them for the sake of backward compatibility. When necessary, a transition strategy for existing users has been designed not to force them running around setting configuration variables and updating their scripts in order to either keep the traditional behaviour or adjust to the new behaviour, on the day their sysadmin decides to install the new version of git. When we switched from "git-foo" to "git foo" in 1.6.0, even though the change had been advertised and the transition guide had been provided for a very long time, the users procrastinated during the entire transtion period, and ended up panicking on the day their sysadmins updated their git installation. We are trying to avoid repeating that unpleasantness in the 1.7.0 release. For changes decided to be in 1.7.0, commands that will be affected have been much louder to strongly discourage such procrastination, and they continue to be in this release. If you have been using recent versions of git, you would have seen warnings issued when you used features whose behaviour will change, with a clear instruction on how to keep the existing behaviour if you want to. You hopefully are already well prepared. Of course, we have also been giving "this and that will change in 1.7.0; prepare yourselves" warnings in the release notes and announcement messages for the past few releases. Let's see how well users will fare this time. * "git push" into a branch that is currently checked out (i.e. pointed by HEAD in a repository that is not bare) will be 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. Versions of git since 1.6.2 have issued a loud warning when you tried to do these operations without setting the configuration, so repositories of people who still need to be able to perform such a push should already have been future proofed. 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 process that already took place so far. * "git send-email" will 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. Git 1.6.6 (this release) will issue a warning about the upcoming default change, when it uses the traditional "deep threading" behaviour as the built-in default. To squelch the warning but still use the "deep threading" behaviour, give --chain-reply-to option or set sendemail.chainreplyto to true. It has been possible to configure send-email to send "shallow thread" by setting sendemail.chainreplyto configuration variable to false. The only thing 1.7.0 release will do is to change the default when you haven't configured that variable. * "git status" will not be "git commit --dry-run". This change does not affect you if you run the command without pathspec. Nobody sane found the current behaviour of "git status Makefile" useful nor meaningful, and it confused users. "git commit --dry-run" has been provided as a way to get the current behaviour of this command since 1.6.5. * "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 1.7.0, the "ignore whitespaces" will affect the semantics of the diff operation itself. A change that does not affect anything but whitespaces will be reported with zero exit status when run with --exit-code, and there will not be "diff --git" header for such a change. Updates since v1.6.5 -------------------- (subsystems) * various gitk updates including use of themed widgets under Tk 8.5, Japanese translation, a fix to a bug when running "gui blame" from a subdirectory, etc. * various git-gui updates including new translations, wm states fixes, Tk bug workaround after quitting, improved heuristics to trigger gc, etc. * various git-svn updates. * "git fetch" over http learned a new mode that is different from the traditional "dumb commit walker". (portability) * imap-send can be built on mingw port. (performance) * "git diff -B" has smaller memory footprint. (usability, bells and whistles) * The object replace mechanism can be bypassed with --no-replace-objects global option given to the "git" program. * In configuration files, a few variables that name paths can begin with ~/ and ~username/ and they are expanded as expected. * "git subcmd -h" now shows short usage help for many more subcommands. * "git bisect reset" can reset to an arbitrary commit. * "git checkout frotz" when there is no local branch "frotz" but there is only one remote tracking branch "frotz" is taken as a request to start the named branch at the corresponding remote tracking branch. * "git commit -c/-C/--amend" can be told with a new "--reset-author" option to ignore authorship information in the commit it is taking the message from. * "git describe" can be told to add "-dirty" suffix with "--dirty" option. * "git diff" learned --submodule option to show a list of one-line logs instead of differences between the commit object names. * "git diff" learned to honor diff.color.func configuration to paint function name hint printed on the hunk header "@@ -j,k +l,m @@" line in the specified color. * "git fetch" learned --all and --multiple options, to run fetch from many repositories, and --prune option to remove remote tracking branches that went stale. These make "git remote update" and "git remote prune" less necessary (there is no plan to remove "remote update" nor "remote prune", though). * "git fsck" by default checks the packfiles (i.e. "--full" is the default); you can turn it off with "git fsck --no-full". * "git grep" can use -F (fixed strings) and -i (ignore case) together. * import-tars contributed fast-import frontend learned more types of compressed tarballs. * "git instaweb" knows how to talk with mod_cgid to apache2. * "git log --decorate" shows the location of HEAD as well. * "git log" and "git rev-list" learned to take revs and pathspecs from the standard input with the new "--stdin" option. * "--pretty=format" option to "log" family of commands learned: . to wrap text with the "%w()" specifier. . to show reflog information with "%g[sdD]" specifier. * "git notes" command to annotate existing commits. * "git merge" (and "git pull") learned --ff-only option to make it fail if the merge does not result in a fast-forward. * "git mergetool" learned to use p4merge. * "git rebase -i" learned "reword" that acts like "edit" but immediately starts an editor to tweak the log message without returning control to the shell, which is done by "edit" to give an opportunity to tweak the contents. * "git send-email" can be told with "--envelope-sender=auto" to use the same address as "From:" address as the envelope sender address. * "git send-email" will issue a warning when it defaults to the --chain-reply-to behaviour without being told by the user and instructs to prepare for the change of the default in 1.7.0 release. * In "git submodule add <repository> <path>", <path> is now optional and inferred from <repository> the same way "git clone <repository>" does. * "git svn" learned to read SVN 1.5+ and SVK merge tickets. * "git svn" learned to recreate empty directories tracked only by SVN. * "gitweb" can optionally render its "blame" output incrementally (this requires JavaScript on the client side). * Author names shown in gitweb output are links to search commits by the author. Fixes since v1.6.5 ------------------ All of the fixes in v1.6.5.X maintenance series are included in this release, unless otherwise noted. 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.
2010-01-15 11:36:41 +01:00
man/man1/git-notes.1
Switch GIT to use a meta-pkg hierarchy like, for example, devel/subversion. Also, update to 1.5.3.7. Fixes since v1.5.3.6 -------------------- * git-send-email added 8-bit contents to the payload without marking it as 8-bit in a CTE header. * "git-bundle create a.bndl HEAD" dereferenced the symref and did not record the ref as 'HEAD'; this prevented a bundle from being used as a normal source of git-clone. * The code to reject nonsense command line of the form "git-commit -a paths..." and "git-commit --interactive paths..." were broken. * Adding a signature that is not ASCII-only to an original commit that is ASCII-only would make the result non-ASCII. "git-format-patch -s" did not mark such a message correctly with MIME encoding header. * git-add sometimes did not mark the resulting index entry stat-clean. This affected only cases when adding the contents with the same length as the previously staged contents, and the previous staging made the index entry "racily clean". * git-commit did not honor GIT_INDEX_FILE the user had in the environment. * When checking out a revision, git-checkout did not report where the updated HEAD is if you happened to have a file called HEAD in the work tree. * "git-rev-list --objects" mishandled a tree that points at a submodule. * "git cvsimport" was not ready for packed refs that "git gc" can produce and gave incorrect results. * Many scripted Porcelains were confused when you happened to have a file called "HEAD" in your work tree. * Miscellaneous updates to the user manual and documentation.
2007-12-12 05:22:20 +01:00
man/man1/git-pack-objects.1
man/man1/git-pack-redundant.1
man/man1/git-pack-refs.1
man/man1/git-parse-remote.1
man/man1/git-patch-id.1
man/man1/git-peek-remote.1
man/man1/git-prune-packed.1
man/man1/git-prune.1
man/man1/git-pull.1
man/man1/git-push.1
man/man1/git-quiltimport.1
man/man1/git-read-tree.1
man/man1/git-rebase.1
man/man1/git-receive-pack.1
man/man1/git-reflog.1
man/man1/git-relink.1
Update to 1.6.6, requested by agc. Git v1.6.6 Release Notes ======================== Notes on behaviour change ------------------------- * In this release, "git fsck" defaults to "git fsck --full" and checks packfiles, and because of this it will take much longer to complete than before. If you prefer a quicker check only on loose objects (the old default), you can say "git fsck --no-full". This has been supported by 1.5.4 and newer versions of git, so it is safe to write it in your script even if you use slightly older git on some of your machines. Preparing yourselves for compatibility issues in 1.7.0 ------------------------------------------------------ In git 1.7.0, which is planned to be the release after 1.6.6, there will be a handful of behaviour changes that will break backward compatibility. These changes were discussed long time ago and existing behaviours have been identified as more problematic to the userbase than keeping them for the sake of backward compatibility. When necessary, a transition strategy for existing users has been designed not to force them running around setting configuration variables and updating their scripts in order to either keep the traditional behaviour or adjust to the new behaviour, on the day their sysadmin decides to install the new version of git. When we switched from "git-foo" to "git foo" in 1.6.0, even though the change had been advertised and the transition guide had been provided for a very long time, the users procrastinated during the entire transtion period, and ended up panicking on the day their sysadmins updated their git installation. We are trying to avoid repeating that unpleasantness in the 1.7.0 release. For changes decided to be in 1.7.0, commands that will be affected have been much louder to strongly discourage such procrastination, and they continue to be in this release. If you have been using recent versions of git, you would have seen warnings issued when you used features whose behaviour will change, with a clear instruction on how to keep the existing behaviour if you want to. You hopefully are already well prepared. Of course, we have also been giving "this and that will change in 1.7.0; prepare yourselves" warnings in the release notes and announcement messages for the past few releases. Let's see how well users will fare this time. * "git push" into a branch that is currently checked out (i.e. pointed by HEAD in a repository that is not bare) will be 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. Versions of git since 1.6.2 have issued a loud warning when you tried to do these operations without setting the configuration, so repositories of people who still need to be able to perform such a push should already have been future proofed. 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 process that already took place so far. * "git send-email" will 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. Git 1.6.6 (this release) will issue a warning about the upcoming default change, when it uses the traditional "deep threading" behaviour as the built-in default. To squelch the warning but still use the "deep threading" behaviour, give --chain-reply-to option or set sendemail.chainreplyto to true. It has been possible to configure send-email to send "shallow thread" by setting sendemail.chainreplyto configuration variable to false. The only thing 1.7.0 release will do is to change the default when you haven't configured that variable. * "git status" will not be "git commit --dry-run". This change does not affect you if you run the command without pathspec. Nobody sane found the current behaviour of "git status Makefile" useful nor meaningful, and it confused users. "git commit --dry-run" has been provided as a way to get the current behaviour of this command since 1.6.5. * "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 1.7.0, the "ignore whitespaces" will affect the semantics of the diff operation itself. A change that does not affect anything but whitespaces will be reported with zero exit status when run with --exit-code, and there will not be "diff --git" header for such a change. Updates since v1.6.5 -------------------- (subsystems) * various gitk updates including use of themed widgets under Tk 8.5, Japanese translation, a fix to a bug when running "gui blame" from a subdirectory, etc. * various git-gui updates including new translations, wm states fixes, Tk bug workaround after quitting, improved heuristics to trigger gc, etc. * various git-svn updates. * "git fetch" over http learned a new mode that is different from the traditional "dumb commit walker". (portability) * imap-send can be built on mingw port. (performance) * "git diff -B" has smaller memory footprint. (usability, bells and whistles) * The object replace mechanism can be bypassed with --no-replace-objects global option given to the "git" program. * In configuration files, a few variables that name paths can begin with ~/ and ~username/ and they are expanded as expected. * "git subcmd -h" now shows short usage help for many more subcommands. * "git bisect reset" can reset to an arbitrary commit. * "git checkout frotz" when there is no local branch "frotz" but there is only one remote tracking branch "frotz" is taken as a request to start the named branch at the corresponding remote tracking branch. * "git commit -c/-C/--amend" can be told with a new "--reset-author" option to ignore authorship information in the commit it is taking the message from. * "git describe" can be told to add "-dirty" suffix with "--dirty" option. * "git diff" learned --submodule option to show a list of one-line logs instead of differences between the commit object names. * "git diff" learned to honor diff.color.func configuration to paint function name hint printed on the hunk header "@@ -j,k +l,m @@" line in the specified color. * "git fetch" learned --all and --multiple options, to run fetch from many repositories, and --prune option to remove remote tracking branches that went stale. These make "git remote update" and "git remote prune" less necessary (there is no plan to remove "remote update" nor "remote prune", though). * "git fsck" by default checks the packfiles (i.e. "--full" is the default); you can turn it off with "git fsck --no-full". * "git grep" can use -F (fixed strings) and -i (ignore case) together. * import-tars contributed fast-import frontend learned more types of compressed tarballs. * "git instaweb" knows how to talk with mod_cgid to apache2. * "git log --decorate" shows the location of HEAD as well. * "git log" and "git rev-list" learned to take revs and pathspecs from the standard input with the new "--stdin" option. * "--pretty=format" option to "log" family of commands learned: . to wrap text with the "%w()" specifier. . to show reflog information with "%g[sdD]" specifier. * "git notes" command to annotate existing commits. * "git merge" (and "git pull") learned --ff-only option to make it fail if the merge does not result in a fast-forward. * "git mergetool" learned to use p4merge. * "git rebase -i" learned "reword" that acts like "edit" but immediately starts an editor to tweak the log message without returning control to the shell, which is done by "edit" to give an opportunity to tweak the contents. * "git send-email" can be told with "--envelope-sender=auto" to use the same address as "From:" address as the envelope sender address. * "git send-email" will issue a warning when it defaults to the --chain-reply-to behaviour without being told by the user and instructs to prepare for the change of the default in 1.7.0 release. * In "git submodule add <repository> <path>", <path> is now optional and inferred from <repository> the same way "git clone <repository>" does. * "git svn" learned to read SVN 1.5+ and SVK merge tickets. * "git svn" learned to recreate empty directories tracked only by SVN. * "gitweb" can optionally render its "blame" output incrementally (this requires JavaScript on the client side). * Author names shown in gitweb output are links to search commits by the author. Fixes since v1.6.5 ------------------ All of the fixes in v1.6.5.X maintenance series are included in this release, unless otherwise noted. 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.
2010-01-15 11:36:41 +01:00
man/man1/git-remote-helpers.1
Switch GIT to use a meta-pkg hierarchy like, for example, devel/subversion. Also, update to 1.5.3.7. Fixes since v1.5.3.6 -------------------- * git-send-email added 8-bit contents to the payload without marking it as 8-bit in a CTE header. * "git-bundle create a.bndl HEAD" dereferenced the symref and did not record the ref as 'HEAD'; this prevented a bundle from being used as a normal source of git-clone. * The code to reject nonsense command line of the form "git-commit -a paths..." and "git-commit --interactive paths..." were broken. * Adding a signature that is not ASCII-only to an original commit that is ASCII-only would make the result non-ASCII. "git-format-patch -s" did not mark such a message correctly with MIME encoding header. * git-add sometimes did not mark the resulting index entry stat-clean. This affected only cases when adding the contents with the same length as the previously staged contents, and the previous staging made the index entry "racily clean". * git-commit did not honor GIT_INDEX_FILE the user had in the environment. * When checking out a revision, git-checkout did not report where the updated HEAD is if you happened to have a file called HEAD in the work tree. * "git-rev-list --objects" mishandled a tree that points at a submodule. * "git cvsimport" was not ready for packed refs that "git gc" can produce and gave incorrect results. * Many scripted Porcelains were confused when you happened to have a file called "HEAD" in your work tree. * Miscellaneous updates to the user manual and documentation.
2007-12-12 05:22:20 +01:00
man/man1/git-remote.1
man/man1/git-repack.1
Update to 1.6.6, requested by agc. Git v1.6.6 Release Notes ======================== Notes on behaviour change ------------------------- * In this release, "git fsck" defaults to "git fsck --full" and checks packfiles, and because of this it will take much longer to complete than before. If you prefer a quicker check only on loose objects (the old default), you can say "git fsck --no-full". This has been supported by 1.5.4 and newer versions of git, so it is safe to write it in your script even if you use slightly older git on some of your machines. Preparing yourselves for compatibility issues in 1.7.0 ------------------------------------------------------ In git 1.7.0, which is planned to be the release after 1.6.6, there will be a handful of behaviour changes that will break backward compatibility. These changes were discussed long time ago and existing behaviours have been identified as more problematic to the userbase than keeping them for the sake of backward compatibility. When necessary, a transition strategy for existing users has been designed not to force them running around setting configuration variables and updating their scripts in order to either keep the traditional behaviour or adjust to the new behaviour, on the day their sysadmin decides to install the new version of git. When we switched from "git-foo" to "git foo" in 1.6.0, even though the change had been advertised and the transition guide had been provided for a very long time, the users procrastinated during the entire transtion period, and ended up panicking on the day their sysadmins updated their git installation. We are trying to avoid repeating that unpleasantness in the 1.7.0 release. For changes decided to be in 1.7.0, commands that will be affected have been much louder to strongly discourage such procrastination, and they continue to be in this release. If you have been using recent versions of git, you would have seen warnings issued when you used features whose behaviour will change, with a clear instruction on how to keep the existing behaviour if you want to. You hopefully are already well prepared. Of course, we have also been giving "this and that will change in 1.7.0; prepare yourselves" warnings in the release notes and announcement messages for the past few releases. Let's see how well users will fare this time. * "git push" into a branch that is currently checked out (i.e. pointed by HEAD in a repository that is not bare) will be 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. Versions of git since 1.6.2 have issued a loud warning when you tried to do these operations without setting the configuration, so repositories of people who still need to be able to perform such a push should already have been future proofed. 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 process that already took place so far. * "git send-email" will 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. Git 1.6.6 (this release) will issue a warning about the upcoming default change, when it uses the traditional "deep threading" behaviour as the built-in default. To squelch the warning but still use the "deep threading" behaviour, give --chain-reply-to option or set sendemail.chainreplyto to true. It has been possible to configure send-email to send "shallow thread" by setting sendemail.chainreplyto configuration variable to false. The only thing 1.7.0 release will do is to change the default when you haven't configured that variable. * "git status" will not be "git commit --dry-run". This change does not affect you if you run the command without pathspec. Nobody sane found the current behaviour of "git status Makefile" useful nor meaningful, and it confused users. "git commit --dry-run" has been provided as a way to get the current behaviour of this command since 1.6.5. * "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 1.7.0, the "ignore whitespaces" will affect the semantics of the diff operation itself. A change that does not affect anything but whitespaces will be reported with zero exit status when run with --exit-code, and there will not be "diff --git" header for such a change. Updates since v1.6.5 -------------------- (subsystems) * various gitk updates including use of themed widgets under Tk 8.5, Japanese translation, a fix to a bug when running "gui blame" from a subdirectory, etc. * various git-gui updates including new translations, wm states fixes, Tk bug workaround after quitting, improved heuristics to trigger gc, etc. * various git-svn updates. * "git fetch" over http learned a new mode that is different from the traditional "dumb commit walker". (portability) * imap-send can be built on mingw port. (performance) * "git diff -B" has smaller memory footprint. (usability, bells and whistles) * The object replace mechanism can be bypassed with --no-replace-objects global option given to the "git" program. * In configuration files, a few variables that name paths can begin with ~/ and ~username/ and they are expanded as expected. * "git subcmd -h" now shows short usage help for many more subcommands. * "git bisect reset" can reset to an arbitrary commit. * "git checkout frotz" when there is no local branch "frotz" but there is only one remote tracking branch "frotz" is taken as a request to start the named branch at the corresponding remote tracking branch. * "git commit -c/-C/--amend" can be told with a new "--reset-author" option to ignore authorship information in the commit it is taking the message from. * "git describe" can be told to add "-dirty" suffix with "--dirty" option. * "git diff" learned --submodule option to show a list of one-line logs instead of differences between the commit object names. * "git diff" learned to honor diff.color.func configuration to paint function name hint printed on the hunk header "@@ -j,k +l,m @@" line in the specified color. * "git fetch" learned --all and --multiple options, to run fetch from many repositories, and --prune option to remove remote tracking branches that went stale. These make "git remote update" and "git remote prune" less necessary (there is no plan to remove "remote update" nor "remote prune", though). * "git fsck" by default checks the packfiles (i.e. "--full" is the default); you can turn it off with "git fsck --no-full". * "git grep" can use -F (fixed strings) and -i (ignore case) together. * import-tars contributed fast-import frontend learned more types of compressed tarballs. * "git instaweb" knows how to talk with mod_cgid to apache2. * "git log --decorate" shows the location of HEAD as well. * "git log" and "git rev-list" learned to take revs and pathspecs from the standard input with the new "--stdin" option. * "--pretty=format" option to "log" family of commands learned: . to wrap text with the "%w()" specifier. . to show reflog information with "%g[sdD]" specifier. * "git notes" command to annotate existing commits. * "git merge" (and "git pull") learned --ff-only option to make it fail if the merge does not result in a fast-forward. * "git mergetool" learned to use p4merge. * "git rebase -i" learned "reword" that acts like "edit" but immediately starts an editor to tweak the log message without returning control to the shell, which is done by "edit" to give an opportunity to tweak the contents. * "git send-email" can be told with "--envelope-sender=auto" to use the same address as "From:" address as the envelope sender address. * "git send-email" will issue a warning when it defaults to the --chain-reply-to behaviour without being told by the user and instructs to prepare for the change of the default in 1.7.0 release. * In "git submodule add <repository> <path>", <path> is now optional and inferred from <repository> the same way "git clone <repository>" does. * "git svn" learned to read SVN 1.5+ and SVK merge tickets. * "git svn" learned to recreate empty directories tracked only by SVN. * "gitweb" can optionally render its "blame" output incrementally (this requires JavaScript on the client side). * Author names shown in gitweb output are links to search commits by the author. Fixes since v1.6.5 ------------------ All of the fixes in v1.6.5.X maintenance series are included in this release, unless otherwise noted. 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.
2010-01-15 11:36:41 +01:00
man/man1/git-replace.1
Switch GIT to use a meta-pkg hierarchy like, for example, devel/subversion. Also, update to 1.5.3.7. Fixes since v1.5.3.6 -------------------- * git-send-email added 8-bit contents to the payload without marking it as 8-bit in a CTE header. * "git-bundle create a.bndl HEAD" dereferenced the symref and did not record the ref as 'HEAD'; this prevented a bundle from being used as a normal source of git-clone. * The code to reject nonsense command line of the form "git-commit -a paths..." and "git-commit --interactive paths..." were broken. * Adding a signature that is not ASCII-only to an original commit that is ASCII-only would make the result non-ASCII. "git-format-patch -s" did not mark such a message correctly with MIME encoding header. * git-add sometimes did not mark the resulting index entry stat-clean. This affected only cases when adding the contents with the same length as the previously staged contents, and the previous staging made the index entry "racily clean". * git-commit did not honor GIT_INDEX_FILE the user had in the environment. * When checking out a revision, git-checkout did not report where the updated HEAD is if you happened to have a file called HEAD in the work tree. * "git-rev-list --objects" mishandled a tree that points at a submodule. * "git cvsimport" was not ready for packed refs that "git gc" can produce and gave incorrect results. * Many scripted Porcelains were confused when you happened to have a file called "HEAD" in your work tree. * Miscellaneous updates to the user manual and documentation.
2007-12-12 05:22:20 +01:00
man/man1/git-repo-config.1
man/man1/git-request-pull.1
man/man1/git-rerere.1
man/man1/git-reset.1
man/man1/git-rev-list.1
man/man1/git-rev-parse.1
man/man1/git-revert.1
man/man1/git-rm.1
man/man1/git-send-email.1
man/man1/git-send-pack.1
man/man1/git-sh-setup.1
man/man1/git-shell.1
man/man1/git-shortlog.1
man/man1/git-show-branch.1
man/man1/git-show-index.1
man/man1/git-show-ref.1
man/man1/git-show.1
Update scmgit{,-base,-docs} to 1.6.2.5. Major changes in 1.6.1: When some commands (e.g. "git log", "git diff") spawn pager internally, we used to make the pager the parent process of the git command that produces output. This meant that the exit status of the whole thing comes from the pager, not the underlying git command. We swapped the order of the processes around and you will see the exit code from the command from now on. Major changes in 1.6.2: With the next major release, "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. 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. For a similar reason, "git push $there :$killed" to delete the branch $killed in a remote repository $there, if $killed branch is the current branch pointed at by its HEAD, gets a large warning. You can choose what should happen upon such a push by setting the configuration variable receive.denyDeleteCurrent in the receiving repository.
2009-05-05 08:21:16 +02:00
man/man1/git-stage.1
Switch GIT to use a meta-pkg hierarchy like, for example, devel/subversion. Also, update to 1.5.3.7. Fixes since v1.5.3.6 -------------------- * git-send-email added 8-bit contents to the payload without marking it as 8-bit in a CTE header. * "git-bundle create a.bndl HEAD" dereferenced the symref and did not record the ref as 'HEAD'; this prevented a bundle from being used as a normal source of git-clone. * The code to reject nonsense command line of the form "git-commit -a paths..." and "git-commit --interactive paths..." were broken. * Adding a signature that is not ASCII-only to an original commit that is ASCII-only would make the result non-ASCII. "git-format-patch -s" did not mark such a message correctly with MIME encoding header. * git-add sometimes did not mark the resulting index entry stat-clean. This affected only cases when adding the contents with the same length as the previously staged contents, and the previous staging made the index entry "racily clean". * git-commit did not honor GIT_INDEX_FILE the user had in the environment. * When checking out a revision, git-checkout did not report where the updated HEAD is if you happened to have a file called HEAD in the work tree. * "git-rev-list --objects" mishandled a tree that points at a submodule. * "git cvsimport" was not ready for packed refs that "git gc" can produce and gave incorrect results. * Many scripted Porcelains were confused when you happened to have a file called "HEAD" in your work tree. * Miscellaneous updates to the user manual and documentation.
2007-12-12 05:22:20 +01:00
man/man1/git-stash.1
man/man1/git-status.1
man/man1/git-stripspace.1
man/man1/git-submodule.1
man/man1/git-svn.1
man/man1/git-symbolic-ref.1
man/man1/git-tag.1
man/man1/git-tar-tree.1
man/man1/git-unpack-file.1
man/man1/git-unpack-objects.1
man/man1/git-update-index.1
man/man1/git-update-ref.1
man/man1/git-update-server-info.1
man/man1/git-upload-archive.1
man/man1/git-upload-pack.1
man/man1/git-var.1
man/man1/git-verify-pack.1
man/man1/git-verify-tag.1
Update devel/scmgit [1.5.4.5 -> 1.5.5] The scmgit-base package now installs most of its binaries, e.g. git-*, to ${PREFIX}/libexec/git-core/ instead of ${PREFIX}/bin. There are only two programs under ${LOCALBASE}/bin: the "master" git(7) wrapper program and the gitk tcl/tk repository browser. Given that there are many different GIT interfaces (GUI applications, devel/tig, shell completion scripts, etc.), it seemed needless to me to have 120+ binaries--a vast majority of which most users would seldom invoke directly--polluting ${LOCALBASE}/bin. GIT v1.5.5 Release Notes ======================== Updates since v1.5.4 -------------------- (subsystems) * Comes with git-gui 0.10.1 (portability) * We shouldn't ask for BSD group ownership semantics by setting g+s bit on directories on older BSD systems that refuses chmod() by non root users. BSD semantics is the default there anyway. * Bunch of portability improvement patches coming from an effort to port to Solaris has been applied. (performance) * On platforms with suboptimal qsort(3) implementation, there is an option to use more reasonable substitute we ship with our software. * New configuration variable "pack.packsizelimit" can be used in place of command line option --max-pack-size. * "git fetch" over the native git protocol used to make a connection to find out the set of current remote refs and another to actually download the pack data. We now use only one connection for these tasks. * "git commit" does not run lstat(2) more than necessary anymore. (usability, bells and whistles) * Bash completion script (in contrib) are aware of more commands and options. * You can be warned when core.autocrlf conversion is applied in such a way that results in an irreversible conversion. * A catch-all "color.ui" configuration variable can be used to enable coloring of all color-capable commands, instead of individual ones such as "color.status" and "color.branch". * The commands refused to take absolute pathnames where they require pathnames relative to the work tree or the current subdirectory. They now can take absolute pathnames in such a case as long as the pathnames do not refer outside of the work tree. E.g. "git add $(pwd)/foo" now works. * Error messages used to be sent to stderr, only to get hidden, when $PAGER was in use. They now are sent to stdout along with the command output to be shown in the $PAGER. * A pattern "foo/" in .gitignore file now matches a directory "foo". Pattern "foo" also matches as before. * bash completion's prompt helper function can talk about operation in-progress (e.g. merge, rebase, etc.). * Configuration variables "url.<usethis>.insteadof = <otherurl>" can be used to tell "git-fetch" and "git-push" to use different URL than what is given from the command line. * "git add -i" behaves better even before you make an initial commit. * "git am" refused to run from a subdirectory without a good reason. * After "git apply --whitespace=fix" fixes whitespace errors in a patch, a line before the fix can appear as a context or preimage line in a later patch, causing the patch not to apply. The command now knows to see through whitespace fixes done to context lines to successfully apply such a patch series. * "git branch" (and "git checkout -b") to branch from a local branch can optionally set "branch.<name>.merge" to mark the new branch to build on the other local branch, when "branch.autosetupmerge" is set to "always", or when passing the command line option "--track" (this option was ignored when branching from local branches). By default, this does not happen when branching from a local branch. * "git checkout" to switch to a branch that has "branch.<name>.merge" set (i.e. marked to build on another branch) reports how much the branch and the other branch diverged. * When "git checkout" has to update a lot of paths, it used to be silent for 4 seconds before it showed any progress report. It is now a bit more impatient and starts showing progress report early. * "git commit" learned a new hook "prepare-commit-msg" that can inspect what is going to be committed and prepare the commit log message template to be edited. * "git cvsimport" can now take more than one -M options. * "git describe" learned to limit the tags to be used for naming with --match option. * "git describe --contains" now barfs when the named commit cannot be described. * "git describe --exact-match" describes only commits that are tagged. * "git describe --long" describes a tagged commit as $tag-0-$sha1, instead of just showing the exact tagname. * "git describe" warns when using a tag whose name and path contradict with each other. * "git diff" learned "--relative" option to limit and output paths relative to the current directory when working in a subdirectory. * "git diff" learned "--dirstat" option to show birds-eye-summary of changes more concisely than "--diffstat". * "git format-patch" learned --cover-letter option to generate a cover letter template. * "git gc" learned --quiet option. * "git gc" now automatically prunes unreachable objects that are two weeks old or older. * "git gc --auto" can be disabled more easily by just setting gc.auto to zero. It also tolerates more packfiles by default. * "git grep" now knows "--name-only" is a synonym for the "-l" option. * "git help <alias>" now reports "'git <alias>' is alias to <what>", instead of saying "No manual entry for git-<alias>". * "git help" can use different backends to show manual pages and this can be configured using "man.viewer" configuration. * "gitk" does not restore window position from $HOME/.gitk anymore (it still restores the size). * "git log --grep=<what>" learned "--fixed-strings" option to look for <what> without treating it as a regular expression. * "git gui" learned an auto-spell checking. * "git push <somewhere> HEAD" and "git push <somewhere> +HEAD" works as expected; they push the current branch (and only the current branch). In addition, HEAD can be written as the value of "remote.<there>.push" configuration variable. * When the configuration variable "pack.threads" is set to 0, "git repack" auto detects the number of CPUs and uses that many threads. * "git send-email" learned to prompt for passwords interactively. * "git send-email" learned an easier way to suppress CC recipients. * "git stash" learned "pop" command, that applies the latest stash and removes it from the stash, and "drop" command to discard the named stash entry. * "git submodule" learned a new subcommand "summary" to show the symmetric difference between the HEAD version and the work tree version of the submodule commits. * Various "git cvsimport", "git cvsexportcommit", "git cvsserver", "git svn" and "git p4" improvements. (internal) * Duplicated code between git-help and git-instaweb that launches user's preferred browser has been refactored. * It is now easier to write test scripts that records known breakages. * "git checkout" is rewritten in C. * "git remote" is rewritten in C. * Two conflict hunks that are separated by a very short span of common lines are now coalesced into one larger hunk, to make the result easier to read. * Run-command API's use of file descriptors is documented clearer and is more consistent now. * diff output can be sent to FILE * that is different from stdout. This will help reimplementing more things in C. Fixes since v1.5.4 ------------------ All of the fixes in v1.5.4 maintenance series are included in this release, unless otherwise noted. * "git-http-push" did not allow deletion of remote ref with the usual "push <remote> :<branch>" syntax. * "git-rebase --abort" did not go back to the right location if "git-reset" was run during the "git-rebase" session. * "git imap-send" without setting imap.host did not error out but segfaulted.
2008-04-21 03:09:51 +02:00
man/man1/git-web--browse.1
Switch GIT to use a meta-pkg hierarchy like, for example, devel/subversion. Also, update to 1.5.3.7. Fixes since v1.5.3.6 -------------------- * git-send-email added 8-bit contents to the payload without marking it as 8-bit in a CTE header. * "git-bundle create a.bndl HEAD" dereferenced the symref and did not record the ref as 'HEAD'; this prevented a bundle from being used as a normal source of git-clone. * The code to reject nonsense command line of the form "git-commit -a paths..." and "git-commit --interactive paths..." were broken. * Adding a signature that is not ASCII-only to an original commit that is ASCII-only would make the result non-ASCII. "git-format-patch -s" did not mark such a message correctly with MIME encoding header. * git-add sometimes did not mark the resulting index entry stat-clean. This affected only cases when adding the contents with the same length as the previously staged contents, and the previous staging made the index entry "racily clean". * git-commit did not honor GIT_INDEX_FILE the user had in the environment. * When checking out a revision, git-checkout did not report where the updated HEAD is if you happened to have a file called HEAD in the work tree. * "git-rev-list --objects" mishandled a tree that points at a submodule. * "git cvsimport" was not ready for packed refs that "git gc" can produce and gave incorrect results. * Many scripted Porcelains were confused when you happened to have a file called "HEAD" in your work tree. * Miscellaneous updates to the user manual and documentation.
2007-12-12 05:22:20 +01:00
man/man1/git-whatchanged.1
man/man1/git-write-tree.1
Update to git-1.5.6. GIT v1.5.6 Release Notes ======================== Updates since v1.5.5 -------------------- (subsystems) * Comes with updated gitk and git-gui. (portability) * git will build on AIX better than before now. * core.ignorecase configuration variable can be used to work better on filesystems that are not case sensitive. * "git init" now autodetects the case sensitivity of the filesystem and sets core.ignorecase accordingly. * cpio is no longer used; neither "curl" binary (libcurl is still used). (documentation) * Many freestanding documentation pages have been converted and made available to "git help" (aka "man git<something>") as section 7 of the manual pages. This means bookmarks to some HTML documentation files may need to be updated (eg "tutorial.html" became "gittutorial.html"). (performance) * "git clone" was rewritten in C. This will hopefully help cloning a repository with insane number of refs. * "git rebase --onto $there $from $branch" used to switch to the tip of $branch only to immediately reset back to $from, smudging work tree files unnecessarily. This has been optimized. * Object creation codepath in "git-svn" has been optimized by enhancing plumbing commands git-cat-file and git-hash-object. (usability, bells and whistles) * "git add -p" (and the "patch" subcommand of "git add -i") can choose to apply (or not apply) mode changes independently from contents changes. * "git bisect help" gives longer and more helpful usage information. * "git bisect" does not use a special branch "bisect" anymore; instead, it does its work on a detached HEAD. * "git branch" (and "git checkout -b") can be told to set up branch.<name>.rebase automatically, so that later you can say "git pull" and magically cause "git pull --rebase" to happen. * "git branch --merged" and "git branch --no-merged" can be used to list branches that have already been merged (or not yet merged) to the current branch. * "git cherry-pick" and "git revert" can add a sign-off. * "git commit" mentions the author identity when you are committing somebody else's changes. * "git diff/log --dirstat" output is consistent between binary and textual changes. * "git filter-branch" rewrites signed tags by demoting them to annotated. * "git format-patch --no-binary" can produce a patch that lack binary changes (i.e. cannot be used to propagate the whole changes) meant only for reviewing. * "git init --bare" is a synonym for "git --bare init" now. * "git gc --auto" honors a new pre-auto-gc hook to temporarily disable it. * "git log --pretty=tformat:<custom format>" gives a LF after each entry, instead of giving a LF between each pair of entries which is how "git log --pretty=format:<custom format>" works. * "git log" and friends learned the "--graph" option to show the ancestry graph at the left margin of the output. * "git log" and friends can be told to use date format that is different from the default via 'log.date' configuration variable. * "git send-email" now can send out messages outside a git repository. * "git send-email --compose" was made aware of rfc2047 quoting. * "git status" can optionally include output from "git submodule summary". * "git svn" learned --add-author-from option to propagate the authorship by munging the commit log message. * new object creation and looking up in "git svn" has been optimized. * "gitweb" can read from a system-wide configuration file. (internal) * "git unpack-objects" and "git receive-pack" is now more strict about detecting breakage in the objects they receive over the wire.
2008-06-24 10:21:04 +02:00
man/man1/git.1
Switch GIT to use a meta-pkg hierarchy like, for example, devel/subversion. Also, update to 1.5.3.7. Fixes since v1.5.3.6 -------------------- * git-send-email added 8-bit contents to the payload without marking it as 8-bit in a CTE header. * "git-bundle create a.bndl HEAD" dereferenced the symref and did not record the ref as 'HEAD'; this prevented a bundle from being used as a normal source of git-clone. * The code to reject nonsense command line of the form "git-commit -a paths..." and "git-commit --interactive paths..." were broken. * Adding a signature that is not ASCII-only to an original commit that is ASCII-only would make the result non-ASCII. "git-format-patch -s" did not mark such a message correctly with MIME encoding header. * git-add sometimes did not mark the resulting index entry stat-clean. This affected only cases when adding the contents with the same length as the previously staged contents, and the previous staging made the index entry "racily clean". * git-commit did not honor GIT_INDEX_FILE the user had in the environment. * When checking out a revision, git-checkout did not report where the updated HEAD is if you happened to have a file called HEAD in the work tree. * "git-rev-list --objects" mishandled a tree that points at a submodule. * "git cvsimport" was not ready for packed refs that "git gc" can produce and gave incorrect results. * Many scripted Porcelains were confused when you happened to have a file called "HEAD" in your work tree. * Miscellaneous updates to the user manual and documentation.
2007-12-12 05:22:20 +01:00
man/man1/gitk.1
man/man5/gitattributes.5
Update to git-1.5.6. GIT v1.5.6 Release Notes ======================== Updates since v1.5.5 -------------------- (subsystems) * Comes with updated gitk and git-gui. (portability) * git will build on AIX better than before now. * core.ignorecase configuration variable can be used to work better on filesystems that are not case sensitive. * "git init" now autodetects the case sensitivity of the filesystem and sets core.ignorecase accordingly. * cpio is no longer used; neither "curl" binary (libcurl is still used). (documentation) * Many freestanding documentation pages have been converted and made available to "git help" (aka "man git<something>") as section 7 of the manual pages. This means bookmarks to some HTML documentation files may need to be updated (eg "tutorial.html" became "gittutorial.html"). (performance) * "git clone" was rewritten in C. This will hopefully help cloning a repository with insane number of refs. * "git rebase --onto $there $from $branch" used to switch to the tip of $branch only to immediately reset back to $from, smudging work tree files unnecessarily. This has been optimized. * Object creation codepath in "git-svn" has been optimized by enhancing plumbing commands git-cat-file and git-hash-object. (usability, bells and whistles) * "git add -p" (and the "patch" subcommand of "git add -i") can choose to apply (or not apply) mode changes independently from contents changes. * "git bisect help" gives longer and more helpful usage information. * "git bisect" does not use a special branch "bisect" anymore; instead, it does its work on a detached HEAD. * "git branch" (and "git checkout -b") can be told to set up branch.<name>.rebase automatically, so that later you can say "git pull" and magically cause "git pull --rebase" to happen. * "git branch --merged" and "git branch --no-merged" can be used to list branches that have already been merged (or not yet merged) to the current branch. * "git cherry-pick" and "git revert" can add a sign-off. * "git commit" mentions the author identity when you are committing somebody else's changes. * "git diff/log --dirstat" output is consistent between binary and textual changes. * "git filter-branch" rewrites signed tags by demoting them to annotated. * "git format-patch --no-binary" can produce a patch that lack binary changes (i.e. cannot be used to propagate the whole changes) meant only for reviewing. * "git init --bare" is a synonym for "git --bare init" now. * "git gc --auto" honors a new pre-auto-gc hook to temporarily disable it. * "git log --pretty=tformat:<custom format>" gives a LF after each entry, instead of giving a LF between each pair of entries which is how "git log --pretty=format:<custom format>" works. * "git log" and friends learned the "--graph" option to show the ancestry graph at the left margin of the output. * "git log" and friends can be told to use date format that is different from the default via 'log.date' configuration variable. * "git send-email" now can send out messages outside a git repository. * "git send-email --compose" was made aware of rfc2047 quoting. * "git status" can optionally include output from "git submodule summary". * "git svn" learned --add-author-from option to propagate the authorship by munging the commit log message. * new object creation and looking up in "git svn" has been optimized. * "gitweb" can read from a system-wide configuration file. (internal) * "git unpack-objects" and "git receive-pack" is now more strict about detecting breakage in the objects they receive over the wire.
2008-06-24 10:21:04 +02:00
man/man5/githooks.5
Switch GIT to use a meta-pkg hierarchy like, for example, devel/subversion. Also, update to 1.5.3.7. Fixes since v1.5.3.6 -------------------- * git-send-email added 8-bit contents to the payload without marking it as 8-bit in a CTE header. * "git-bundle create a.bndl HEAD" dereferenced the symref and did not record the ref as 'HEAD'; this prevented a bundle from being used as a normal source of git-clone. * The code to reject nonsense command line of the form "git-commit -a paths..." and "git-commit --interactive paths..." were broken. * Adding a signature that is not ASCII-only to an original commit that is ASCII-only would make the result non-ASCII. "git-format-patch -s" did not mark such a message correctly with MIME encoding header. * git-add sometimes did not mark the resulting index entry stat-clean. This affected only cases when adding the contents with the same length as the previously staged contents, and the previous staging made the index entry "racily clean". * git-commit did not honor GIT_INDEX_FILE the user had in the environment. * When checking out a revision, git-checkout did not report where the updated HEAD is if you happened to have a file called HEAD in the work tree. * "git-rev-list --objects" mishandled a tree that points at a submodule. * "git cvsimport" was not ready for packed refs that "git gc" can produce and gave incorrect results. * Many scripted Porcelains were confused when you happened to have a file called "HEAD" in your work tree. * Miscellaneous updates to the user manual and documentation.
2007-12-12 05:22:20 +01:00
man/man5/gitignore.5
man/man5/gitmodules.5
Update to git-1.5.6. GIT v1.5.6 Release Notes ======================== Updates since v1.5.5 -------------------- (subsystems) * Comes with updated gitk and git-gui. (portability) * git will build on AIX better than before now. * core.ignorecase configuration variable can be used to work better on filesystems that are not case sensitive. * "git init" now autodetects the case sensitivity of the filesystem and sets core.ignorecase accordingly. * cpio is no longer used; neither "curl" binary (libcurl is still used). (documentation) * Many freestanding documentation pages have been converted and made available to "git help" (aka "man git<something>") as section 7 of the manual pages. This means bookmarks to some HTML documentation files may need to be updated (eg "tutorial.html" became "gittutorial.html"). (performance) * "git clone" was rewritten in C. This will hopefully help cloning a repository with insane number of refs. * "git rebase --onto $there $from $branch" used to switch to the tip of $branch only to immediately reset back to $from, smudging work tree files unnecessarily. This has been optimized. * Object creation codepath in "git-svn" has been optimized by enhancing plumbing commands git-cat-file and git-hash-object. (usability, bells and whistles) * "git add -p" (and the "patch" subcommand of "git add -i") can choose to apply (or not apply) mode changes independently from contents changes. * "git bisect help" gives longer and more helpful usage information. * "git bisect" does not use a special branch "bisect" anymore; instead, it does its work on a detached HEAD. * "git branch" (and "git checkout -b") can be told to set up branch.<name>.rebase automatically, so that later you can say "git pull" and magically cause "git pull --rebase" to happen. * "git branch --merged" and "git branch --no-merged" can be used to list branches that have already been merged (or not yet merged) to the current branch. * "git cherry-pick" and "git revert" can add a sign-off. * "git commit" mentions the author identity when you are committing somebody else's changes. * "git diff/log --dirstat" output is consistent between binary and textual changes. * "git filter-branch" rewrites signed tags by demoting them to annotated. * "git format-patch --no-binary" can produce a patch that lack binary changes (i.e. cannot be used to propagate the whole changes) meant only for reviewing. * "git init --bare" is a synonym for "git --bare init" now. * "git gc --auto" honors a new pre-auto-gc hook to temporarily disable it. * "git log --pretty=tformat:<custom format>" gives a LF after each entry, instead of giving a LF between each pair of entries which is how "git log --pretty=format:<custom format>" works. * "git log" and friends learned the "--graph" option to show the ancestry graph at the left margin of the output. * "git log" and friends can be told to use date format that is different from the default via 'log.date' configuration variable. * "git send-email" now can send out messages outside a git repository. * "git send-email --compose" was made aware of rfc2047 quoting. * "git status" can optionally include output from "git submodule summary". * "git svn" learned --add-author-from option to propagate the authorship by munging the commit log message. * new object creation and looking up in "git svn" has been optimized. * "gitweb" can read from a system-wide configuration file. (internal) * "git unpack-objects" and "git receive-pack" is now more strict about detecting breakage in the objects they receive over the wire.
2008-06-24 10:21:04 +02:00
man/man5/gitrepository-layout.5
man/man7/gitcli.7
man/man7/gitcore-tutorial.7
man/man7/gitcvs-migration.7
man/man7/gitdiffcore.7
man/man7/gitglossary.7
Changes 1.7.3.2: This is primarily to push out many documentation fixes accumulated since the 1.7.3.1 release. Changes 1.7.3.1: * "git stash show stash@{$n}" was accidentally broken in 1.7.3 ("git stash show" without any argument still worked, though). * "git stash branch $branch stash@{$n}" was accidentally broken in 1.7.3 and started dropping the named stash even when branch creation failed. Changes 1.7.3: * git-gui, now at version 0.13.0, got various updates and a new maintainer, Pat Thoyts. * Gitweb allows its configuration to change per each request; it used to read the configuration once upon startup. * When git finds a corrupt object, it now reports the file that contains it. * "git checkout -B <it>" is a shorter way to say "git branch -f <it>" followed by "git checkout <it>". * When "git checkout" or "git merge" refuse to proceed in order to protect local modification to your working tree, they used to stop after showing just one path that might be lost. They now show all, in a format that is easier to read. * "git clean" learned "-e" ("--exclude") option. * Hunk headers produced for C# files by "git diff" and friends show more relevant context than before. * diff.ignoresubmodules configuration variable can be used to squelch the differences in submodules reported when running commands (e.g. "diff", "status", etc.) at the superproject level. * http.useragent configuration can be used to lie who you are to your restrictive firewall. * "git rebase --strategy <s>" learned "-X" option to pass extra options that are understood by the chosen merge strategy. * "git rebase -i" learned "exec" that you can insert into the insn sheet to run a command between its steps. * "git rebase" between branches that have many binary changes that do not conflict should be faster. * "git rebase -i" peeks into rebase.autosquash configuration and acts as if you gave --autosquash from the command line.
2010-10-28 12:23:07 +02:00
man/man7/gitrevisions.7
Update to git-1.5.6. GIT v1.5.6 Release Notes ======================== Updates since v1.5.5 -------------------- (subsystems) * Comes with updated gitk and git-gui. (portability) * git will build on AIX better than before now. * core.ignorecase configuration variable can be used to work better on filesystems that are not case sensitive. * "git init" now autodetects the case sensitivity of the filesystem and sets core.ignorecase accordingly. * cpio is no longer used; neither "curl" binary (libcurl is still used). (documentation) * Many freestanding documentation pages have been converted and made available to "git help" (aka "man git<something>") as section 7 of the manual pages. This means bookmarks to some HTML documentation files may need to be updated (eg "tutorial.html" became "gittutorial.html"). (performance) * "git clone" was rewritten in C. This will hopefully help cloning a repository with insane number of refs. * "git rebase --onto $there $from $branch" used to switch to the tip of $branch only to immediately reset back to $from, smudging work tree files unnecessarily. This has been optimized. * Object creation codepath in "git-svn" has been optimized by enhancing plumbing commands git-cat-file and git-hash-object. (usability, bells and whistles) * "git add -p" (and the "patch" subcommand of "git add -i") can choose to apply (or not apply) mode changes independently from contents changes. * "git bisect help" gives longer and more helpful usage information. * "git bisect" does not use a special branch "bisect" anymore; instead, it does its work on a detached HEAD. * "git branch" (and "git checkout -b") can be told to set up branch.<name>.rebase automatically, so that later you can say "git pull" and magically cause "git pull --rebase" to happen. * "git branch --merged" and "git branch --no-merged" can be used to list branches that have already been merged (or not yet merged) to the current branch. * "git cherry-pick" and "git revert" can add a sign-off. * "git commit" mentions the author identity when you are committing somebody else's changes. * "git diff/log --dirstat" output is consistent between binary and textual changes. * "git filter-branch" rewrites signed tags by demoting them to annotated. * "git format-patch --no-binary" can produce a patch that lack binary changes (i.e. cannot be used to propagate the whole changes) meant only for reviewing. * "git init --bare" is a synonym for "git --bare init" now. * "git gc --auto" honors a new pre-auto-gc hook to temporarily disable it. * "git log --pretty=tformat:<custom format>" gives a LF after each entry, instead of giving a LF between each pair of entries which is how "git log --pretty=format:<custom format>" works. * "git log" and friends learned the "--graph" option to show the ancestry graph at the left margin of the output. * "git log" and friends can be told to use date format that is different from the default via 'log.date' configuration variable. * "git send-email" now can send out messages outside a git repository. * "git send-email --compose" was made aware of rfc2047 quoting. * "git status" can optionally include output from "git submodule summary". * "git svn" learned --add-author-from option to propagate the authorship by munging the commit log message. * new object creation and looking up in "git svn" has been optimized. * "gitweb" can read from a system-wide configuration file. (internal) * "git unpack-objects" and "git receive-pack" is now more strict about detecting breakage in the objects they receive over the wire.
2008-06-24 10:21:04 +02:00
man/man7/gittutorial-2.7
man/man7/gittutorial.7
Update scmgit{,-base,-docs} to 1.6.2.5. Major changes in 1.6.1: When some commands (e.g. "git log", "git diff") spawn pager internally, we used to make the pager the parent process of the git command that produces output. This meant that the exit status of the whole thing comes from the pager, not the underlying git command. We swapped the order of the processes around and you will see the exit code from the command from now on. Major changes in 1.6.2: With the next major release, "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. 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. For a similar reason, "git push $there :$killed" to delete the branch $killed in a remote repository $there, if $killed branch is the current branch pointed at by its HEAD, gets a large warning. You can choose what should happen upon such a push by setting the configuration variable receive.denyDeleteCurrent in the receiving repository.
2009-05-05 08:21:16 +02:00
man/man7/gitworkflows.7
Reference in a new issue Copy permalink