43 commits
Author | SHA1 | Message | Date | |
---|---|---|---|---|
sbd
|
cdc9cd88b2 | Honor ${PKGMANDIR} | ||
morr
|
8bcf13b9d5 |
Update to version 1.7.0.5.
ChangeLogs: Updates since v1.6.6 -------------------- (subsystems) * "git fast-import" updates; adds "option" and "feature" to detect the mismatch between fast-import and the frontends that produce the input stream. * "git svn" support of subversion "merge tickets" and miscellaneous fixes. * "gitk" and "git gui" translation updates. * "gitweb" updates (code clean-up, load checking etc.) (portability) * Some more MSVC portability patches for msysgit port. * Minimum Pthreads emulation for msysgit port. (performance) * More performance improvement patches for msysgit port. (usability, bells and whistles) * More commands learned "--quiet" and "--[no-]progress" options. * Various commands given by the end user (e.g. diff.type.textconv, and GIT_EDITOR) can be specified with command line arguments. E.g. it is now possible to say "[diff "utf8doc"] textconv = nkf -w". * "sparse checkout" feature allows only part of the work tree to be checked out. * HTTP transfer can use authentication scheme other than basic (i.e./e.g. digest). * Switching from a version of superproject that used to have a submodule to another version of superproject that no longer has it did not remove the submodule directory when it should (namely, when you are not interested in the submodule at all and didn't clone/checkout). * A new attribute conflict-marker-size can be used to change the size of the conflict markers from the default 7; this is useful when tracked contents (e.g. git-merge documentation) have strings that resemble the conflict markers. * A new syntax "<branch>@{upstream}" can be used on the command line to substitute the name of the "upstream" of the branch. Missing branch defaults to the current branch, so "git fetch && git merge @{upstream}" will be equivalent to "git pull". * "git am --resolved" has a synonym "git am --continue". * "git branch --set-upstream" can be used to update the (surprise!) upstream, i.e. where the branch is supposed to pull and merge from (or rebase onto). * "git checkout A...B" is a way to detach HEAD at the merge base between A and B. * "git checkout -m path" to reset the work tree file back into the conflicted state works even when you already ran "git add path" and resolved the conflicts. * "git commit --date='<date>'" can be used to override the author date just like "git commit --author='<name> <email>'" can be used to override the author identity. * "git commit --no-status" can be used to omit the listing of the index and the work tree status in the editor used to prepare the log message. * "git commit" warns a bit more aggressively until you configure user.email, whose default value almost always is not (and fundamentally cannot be) what you want. * "git difftool" has been extended to make it easier to integrate it with gitk. * "git fetch --all" can now be used in place of "git remote update". * "git grep" does not rely on external grep anymore. It can use more than one thread to accelerate the operation. * "git grep" learned "--quiet" option. * "git log" and friends learned "--glob=heads/*" syntax that is a more flexible way to complement "--branches/--tags/--remotes". * "git merge" learned to pass options specific to strategy-backends. E.g. - "git merge -Xsubtree=path/to/directory" can be used to tell the subtree strategy how much to shift the trees explicitly. - "git merge -Xtheirs" can be used to auto-merge as much as possible, while discarding your own changes and taking merged version in conflicted regions. * "git push" learned "git push origin --delete branch", a syntactic sugar for "git push origin :branch". * "git push" learned "git push --set-upstream origin forker:forkee" that lets you configure your "forker" branch to later pull from "forkee" branch at "origin". * "git rebase --onto A...B" means the history is replayed on top of the merge base between A and B. * "git rebase -i" learned new action "fixup" that squashes the change but does not affect existing log message. * "git rebase -i" also learned --autosquash option that is useful together with the new "fixup" action. * "git remote" learned set-url subcommand that updates (surprise!) url for an existing remote nickname. * "git rerere" learned "forget path" subcommand. Together with "git checkout -m path" it will be useful when you recorded a wrong resolution. * Use of "git reset --merge" has become easier when resetting away a conflicted mess left in the work tree. * "git rerere" had rerere.autoupdate configuration but there was no way to countermand it from the command line; --no-rerere-autoupdate option given to "merge", "revert", etc. fixes this. * "git status" learned "-s(hort)" output format. (developers) * The infrastructure to build foreign SCM interface has been updated. * Many more commands are now built-in. * THREADED_DELTA_SEARCH is no more. If you build with threads, delta compression will always take advantage of it. Fixes since v1.6.6 ------------------ * "git branch -d branch" used to refuse deleting the branch even when the branch is fully merged to its upstream branch if it is not merged to the current branch. It now deletes it in such a case. * "fiter-branch" command incorrectly said --prune-empty and --filter-commit were incompatible; the latter should be read as --commit-filter. * When using "git status" or asking "git diff" to compare the work tree with something, they used to consider that a checked-out submodule with uncommitted changes is not modified; this could cause people to forget committing these changes in the submodule before committing in the superproject. They now consider such a change as a modification and "git diff" will append a "-dirty" to the work tree side when generating patch output or when used with the --submodule option. Fixes since v1.7.0 ------------------ * In a freshly created repository "rev-parse HEAD^0" complained that it is dangling symref, even though "rev-parse HEAD" didn't. * "git show :no-such-name" tried to access the index without bounds check, leading to a potential segfault. * Message from "git cherry-pick" was harder to read and use than necessary when it stopped due to conflicting changes. * We referred to ".git/refs/" throughout the documentation when we meant to talk about abstract notion of "ref namespace". Because people's repositories often have packed refs these days, this was confusing. * "git diff --output=/path/that/cannot/be/written" did not correctly error out. * "git grep -e -pattern-that-begin-with-dash paths..." could not be spelled as "git grep -- -pattern-that-begin-with-dash paths..." which would be a GNU way to use "--" as "end of options". * "git grep" compiled with threading support tried to access an uninitialized mutex on boxes with a single CPU. * "git stash pop -q --index" failed because the unnecessary --index option was propagated to "git stash drop" that is internally run at the end. Fixes since v1.7.0.1 -------------------- * GIT_PAGER was not honored consistently by some scripted Porcelains, most notably "git am". * updating working tree files after telling git to add them to the index and while it is still working created garbage object files in the repository without diagnosing it as an error. * "git bisect -- pathspec..." did not diagnose an error condition properly when the simplification with given pathspec made the history empty. * "git rev-list --cherry-pick A...B" now has an obvious optimization when the histories haven't diverged (i.e. when one end is an ancestor of the other). * "git diff --quiet -w" did not work as expected. * "git fast-import" didn't work with a large input, as it lacked support for producing the pack index in v2 format. * "git imap-send" didn't use CRLF line endings over the imap protocol when storing its payload to the draft box, violating RFC 3501. * "git log --format='%w(x,y,z)%b'" and friends that rewrap message has been optimized for utf-8 payload. * Error messages generated on the receiving end did not come back to "git push". * "git status" in 1.7.0 lacked the optimization we used to have in 1.6.X * "gitweb" did not diagnose parsing errors properly while reading tis configuration file. Fixes since v1.7.0.2 -------------------- * Object files are created in a more ACL friendly way in repositories where group permission is ACL controlled. * "git add -i" didn't handle a deleted path very well. * "git blame" padded line numbers with one extra SP when the total number of lines was one less than multiple of ten due to an off-by-one error. * "git fetch --all/--multi" used to discard information for remotes that are fetched earlier. * "git log --author=me --grep=it" tried to find commits that have "it" or are written by "me", instead of the ones that have "it" _and_ are written by "me". * "git log -g branch" misbehaved when there was no entries in the reflog for the named branch. * "git mailinfo" (hence "git am") incorrectly removed initial indent from paragraphs. * "git prune" and "git reflog" (hence "git gc" as well) didn't honor an instruction never to expire by setting gc.reflogexpire to never. * "git push" misbehaved when branch.<name>.merge was configured without matching branch.<name>.remote. Fixes since v1.7.0.3 -------------------- * Optimized ntohl/htonl on big-endian machines were broken. * Color values given to "color.<cmd>.<slot>" configuration can now have more than one attributes (e.g. "bold ul"). * "git add -u nonexistent-path" did not complain. * "git apply --whitespace=fix" didn't work well when an early patch in a patch series adds trailing blank lines and a later one depended on such a block of blank lines at the end. * "git fast-export" didn't check error status and stop when marks file cannot be opened. * "git format-patch --ignore-if-in-upstream" gave unwarranted errors when the range was empty, instead of silently finishing. * "git remote prune" did not detect remote tracking refs that became dangling correctly. Fixes since v1.7.0.4 -------------------- * "git daemon" failed to compile on platforms without sockaddr_storage type. * Output from "git rev-list --pretty=oneline" was unparsable when a commit did not have any message, which is abnormal but possible in a repository converted from foreign scm. * "git stash show <commit-that-is-not-a-stash>" gave an error message that was not so useful. Reworded the message to "<it> is not a stash". * Python scripts in contrib/ area now start with "#!/usr/bin/env python" to honor user's PATH. * "git imap-send" used to mistake any line that begins with "From " as a message separator in format-patch output. * Smart http server backend failed to report an internal server error and infinitely looped instead after output pipe was closed. |
||
obache
|
e41a9cacd5 |
Fix _XOPEN_SOURCE problem on DragonFly.
Patch provided by YONETANI Tomokazu in PR#43020, and it had been accepted by upstream. |
||
gdt
|
c630833b7e |
Add patch to fix upstream bug where the presence of bswap32 is wrongly
interpreted as our platform being little endian. With this, make check does vastly better on sparc64. PKGREVISION++. From Holger Weiß on pkgsrc-users. |
||
adam
|
b62c0335b3 | PLIST fix for Mac OS X | ||
obache
|
7fb41a57e0 | conflicts with misc/git are resolved with git-4.9.5nb1. | ||
minskim
|
c1abb79d5c |
Update scmgit packages to 1.6.6.2.
Changes: * recursive merge didn't correctly diagnose its own programming errors, and instead caused the caller to segfault. * The new "smart http" aware clients probed the web servers to see if they support smart http, but did not fall back to dumb http transport correctly with some servers. * Time based reflog syntax e.g. "@{yesterday}" didn't diagnose a misspelled time specification and instead assumed "@{now}". * "git archive HEAD -- no-such-directory" produced an empty archive without complaining. * "git blame -L start,end -- file" misbehaved when given a start that is larger than the number of lines in the file. * "git checkout -m" didn't correctly call custom merge backend supplied by the end user. * "git config -f <file>" misbehaved when run from a subdirectory. * "git cvsserver" didn't like having regex metacharacters (e.g. '+') in CVSROOT environment. * "git fast-import" did not correctly handle large blobs that may bust the pack size limit. * "git gui" is supposed to work even when launched from inside a .git directory. * "git gui" misbehaved when applying a hunk that ends with deletion. * "git imap-send" did not honor imap.preformattedHTML as documented. * "git log" family incorrectly showed the commit notes unconditionally by mistake, which was especially irritating when running "git log --oneline". * "git status" shouldn't require an write access to the repository. * Other minor documentation updates are included. |
||
minskim
|
4d9d7395f3 |
Update scmgit to 1.6.6.1.
Changes: * "git blame" did not work well when commit lacked the author name. * "git branch -a name" wasn't diagnosed as an error. * "git count-objects" did not handle packfiles that are bigger than 4G on platforms with 32-bit off_t. * "git checkout -m other" while on a branch that does not have any commit segfaulted, instead of failing. * "git fast-import" choked when fed a tag that do not point at a commit. * "git grep" finding from work tree files could have fed garbage to the underlying regexec(3). * "git grep -L" didn't show empty files (they should never match, and they should always appear in -L output as unmatching). * "git rebase -i" did not abort cleanly if it failed to launch the editor. * "git reset --hard" did not work correctly when GIT_WORK_TREE environment variable is used to point at the root of the true work tree. * http-backend was not listed in the command list in the documentation. * Building on FreeBSD (both 7 and 8) needs OLD_ICONV set in the Makefile * "git checkout -m some-branch" while on an unborn branch crashed. |
||
wiz
|
579796a3e5 | Recursive PKGREVISION bump for jpeg update to 8. | ||
wiz
|
aabd19b641 |
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. |
||
fhajny
|
3035749b63 |
Fix PR 41683
Stop auto-activating hook scripts on new repositories. Bump PKGREVISION. |
||
wiz
|
3f0f7c2c40 |
Wrap 'cd -P' replacement code in platform ifdefs.
From Steven Drake in PR 42168. |
||
wiz
|
ce7507c32c |
Fix PR 42168:
Remove '-P' argument from cd. Bump PKGREVISION. |
||
minskim
|
5386f3fcf6 |
Update scmgit{,-base,-docs} to 1.6.4.
Major changes: * git-svn updates, including a new --authors-prog option to map author names by invoking an external program, 'git svn reset' to unwind 'git svn fetch', support for more than one branches, documenting of the useful --minimize-url feature, new "git svn gc" command, etc. * We feed iconv with "UTF-8" instead of "utf8"; the former is understood more widely. Similarly updated test scripts to use encoding names more widely understood (e.g. use "ISO8859-1" instead of "ISO-8859-1"). * Various portability fixes/workarounds for different vintages of SunOS, IRIX, and Windows. * Git-over-ssh transport on Windows supports PuTTY plink and TortoisePlink. * Many repeated use of lstat() are optimized out in "checkout" codepath. * git-status (and underlying git-diff-index --cached) are optimized to take advantage of cache-tree information in the index. |
||
hasso
|
6af7ed2ad0 | Make it build on DragonFly again. | ||
minskim
|
97731da82d |
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. |
||
joerg
|
7fdde28ea5 | Convert @exec/@unexec to @pkgdir or drop it. | ||
joerg
|
bacea7cad5 | Remove @dirrm entries from PLISTs | ||
minskim
|
6c88932bbb |
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. |
||
tonnerre
|
ef756e22cf |
Upgrade devel/scmgit to version 1.6.0.6 (from 1.6.0.2), in order to fix
security issues and to prepare for the outstanding upgrade of gitweb. Changes since git 1.6.0.2: - Fix output line format for zip archive generation. - Fix continuation of git rebase -i in case of modified files (conflict). - Honor the pre-rebase hook for git rebase -i. - Fix inconsistent behavior of git diff --quiet and diff --exit-code. - Use multiple element hunk headers from git diff correctly. - Portability fix for the git diff hunk header regexps. - Fix git index-pack inside .git/objects/pack directory. - Fix git index-pack in thin-pack mode. - Some git stash apply fixes. - Fixed format string vulnerabilities (e.g. in git remote). - Fix behavior of git checkout -b <existingbranch>. - Make git checkout -q actually quiet. - In quiet remote operation, we don't need the remote side to send along all the statistics we discard. - Don't do cross-directory renames when creating packs. - git prune now also removes stale temp files under .git/objects/pack. - Have git merge prune empty directories. - Have git merge allocate enough memory for the structure itself when enumerating the parents of the resulting commit. - Stop git blame -C -C from segfaulting if it encounters a submodule reference. - If only file times were changed, don't have git rm claim local modifications. - If set-tree fails, don't let git svn output Perl compile errors. - Fix various NULL pointer crashes (e.g. in apply, reset, update-index). - Remove bash completion support for various non-space tools. - Don't have git add -p claim no changes if binary files have been modified. - Fix git archive in bare repositories. - Have git diff display the number of new or deleted files for the case where there have been too many of them to allow rename detection. - Fix git push --mirror to not try to send the stash. - If the remote end is up to date, still update the tracking reference upon git push. - Make git pull $there $branch:$current_branch work on unborn branches. - Have git reset --hard remove new paths after giving up resolving a conflicting merge. - Fix git send-email fd leak in directory scanning. - Make submodule directories appear as tracked in git status. - Have git svn invoke "git command" rather than "git-command". - Have git update-ref -d honor --no-deref. - Fix various memory leaks. - Fix git checkout segfault when HEAD points to a deleted branch. - Allow switching out of the current branch with git checkout on an un-checked-out state. - Have git fast-export export all tags. - Make git ls-files --with-tree=<tree> work with options other than -c. - If the first object in git pack-objects exceeds --max-pack-size, don't stuff even more objects in. - Stop git-p4 from replacing multilike keywords. (They don't exist.) - Make git tag complain about mutually incompatible options. - Fix performance for git internal diff on large files with repeating chunks. - Don't let git repack grab objects out of packs marked with .keep into new packs. - Fix git fsck deep recursion. - Fix git fast-export and fast-import on old style annotated tags without tagger information. - Have git mergetool honor the "--". - Fix segfault of git show <tag> where <tag> points at a nonexistent object. - Fix handling of lists of mail addresses for git send-email. - Fix branch ancestry logic in git svn if the history fetching process was interrupted. |
||
he
|
b021813da0 |
Bump the PKGREVISION for all packages which depend directly on perl,
to trigger/signal a rebuild for the transition 5.8.8 -> 5.10.0. The list of packages is computed by finding all packages which end up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl, or PERL5_PACKLIST defined in their make setup (tested via "make show-vars VARNAMES=..."). |
||
minskim
|
7f246a0de4 |
Add an @exec entry to PLIST to make the binary package work.
Bump PKGREVISION. |
||
uebayasi
|
34004f51e0 |
Move mk/emacs.mk to editors/emacs/modules.mk.
Don't call pkg_info to get the installed Emacs version; always use the version matching EMACS_TYPE set by users. Be DEPENDS to it. This should address pkg/37146 by Aleksey Cheusov. While here convert some emacs lisp packages to user-destdir. |
||
minskim
|
b67702e3ba |
Add a missing entry to PLIST.
Bump PKGREVISION. |
||
bjs
|
cb19d1e93d |
Update to scmgit-1.6.0.2. In pkgsrc, in Makefile.common .include,
change ${.CURDIR}/../... to ../../devel/scmgit/...; makes a lot more sense. Fixes since v1.6.0.1 -------------------- * Installation on platforms that needs .exe suffix to git-* programs were broken in 1.6.0.1. * Installation on filesystems without symbolic links support did nto work well. * In-tree documentations and test scripts now use "git foo" form to set a better example, instead of the "git-foo" form (which is an acceptable form if you have "PATH=$(git --exec-path):$PATH" in your script) * Many commands did not use the correct working tree location when used with GIT_WORK_TREE environment settings. * Some systems needs to use compatibility fnmach and regex libraries independent from each other; the compat/ area has been reorganized to allow this. * "git apply --unidiff-zero" incorrectly applied a -U0 patch that inserts a new line before the second line. * "git blame -c" did not exactly work like "git annotate" when range boundaries are involved. * "git checkout file" when file is still unmerged checked out contents from a random high order stage, which was confusing. * "git clone $there $here/" with extra trailing slashes after explicit local directory name $here did not work as expected. * "git diff" on tracked contents with CRLF line endings did not drive "less" intelligently when showing added or removed lines. * "git diff --dirstat -M" did not add changes in subdirectories up correctly for renamed paths. * "git diff --cumulative" did not imply "--dirstat". * "git for-each-ref refs/heads/" did not work as expected. * "git gui" allowed users to feed patch without any context to be applied. * "git gui" botched parsing "diff" output when a line that begins with two dashes and a space gets removed or a line that begins with two pluses and a space gets added. * "git gui" translation updates and i18n fixes. * "git index-pack" is more careful against disk corruption while completing a thin pack. * "git log -i --grep=pattern" did not ignore case; neither "git log -E --grep=pattern" triggered extended regexp. * "git log --pretty="%ad" --date=short" did not use short format when showing the timestamp. * "git log --author=author" match incorrectly matched with the timestamp part of "author " line in commit objects. * "git log -F --author=author" did not work at all. * Build procedure for "git shell" that used stub versions of some functions and globals was not understood by linkers on some platforms. * "git stash" was fooled by a stat-dirty but otherwise unmodified paths and refused to work until the user refreshed the index. * "git svn" was broken on Perl before 5.8 with recent fixes to reduce use of temporary files. * "git verify-pack -v" did not work correctly when given more than one packfile. Also contains many documentation updates. |
||
bjs
|
5ed1cc309b |
Update to scmgit-1.6.0.1.
GIT v1.6.0.1 Release Notes ========================== Fixes since v1.6.0 ------------------ * "git diff --cc" did not honor content mangling specified by gitattributes and core.autocrlf when reading from the work tree. * "git diff --check" incorrectly detected new trailing blank lines when whitespace check was in effect. * "git for-each-ref" tried to dereference NULL when asked for '%(body)" on a tag with a single incomplete line as its payload. * "git format-patch" peeked before the beginning of a string when "format.headers" variable is empty (a misconfiguration). * "git help help" did not work correctly. * "git mailinfo" (hence "git am") was unhappy when MIME multipart message contained garbage after the finishing boundary. * "git mailinfo" also was unhappy when the "From: " line only had a bare e-mail address. * "git merge" did not refresh the index correctly when a merge resulted in a fast-forward. * "git merge" did not resolve a truly trivial merges that can be done without content level merges. * "git svn dcommit" to a repository with URL that has embedded usernames did not work correctly. * Contains other various documentation fixes. |
||
bjs
|
4a27c47b98 |
+========================+
|GIT v1.6.0 Release Notes| +========================+ User visible changes - Templates now installed in ${PREFIX}/share/examples/scmgit/templates and registered as REQD_FILES. Template subdirectories are registered in MAKE_DIRS. - Installing the many git-foo binaries/scripts into libexec/git-core is now default and better supported. If you've written any scripts or use any applications which expect the git-foo commands to be in ${PREFIX}/bin, please do update them accordingly. +--------------------+ |Updates since v1.5.6| +--------------------+ (subsystems) * git-p4 in contrib learned "allowSubmit" configuration to control on which branch to allow "submit" subcommand. * git-gui learned to stage changes per-line. (portability) * Changes for MinGW port have been merged, thanks to Johannes Sixt and gangs. * Sample hook scripts shipped in templates/ are now suffixed with *.sample. (documentation) * Updated howto/update-hook-example * Got rid of usage of "git-foo" from the tutorial and made typography more consistent. * Disambiguating "--" between revs and paths is finally documented. (performance, robustness, sanity etc.) * index-pack used too much memory when dealing with a deep delta chain. This has been optimized. * reduced excessive inlining to shrink size of the "git" binary. * verify-pack checks the object CRC when using version 2 idx files. * When an object is corrupt in a pack, the object became unusable even when the same object is available in a loose form, We now try harder to fall back to these redundant objects when able. In particular, "git repack -a -f" can be used to fix such a corruption as long as necessary objects are available. * Performance of "git-blame -C -C" operation is vastly improved. * git-clone does not create refs in loose form anymore (it behaves as if you immediately ran git-pack-refs after cloning). This will help repositories with insanely large number of refs. * core.fsyncobjectfiles configuration can be used to ensure that the loose objects created will be fsync'ed (this is only useful on filesystems that does not order data writes properly). * "git commit-tree" plumbing can make Octopus with more than 16 parents. "git commit" has been capable of this for quite some time. (usability, bells and whistles) * even more documentation pages are now accessible via "man" and "git help". * A new environment variable GIT_CEILING_DIRECTORIES can be used to stop the discovery process of the toplevel of working tree; this may be useful when you are working in a slow network disk and are outside any working tree, as bash-completion and "git help" may still need to run in these places. * By default, stash entries never expire. Set reflogexpire in [gc "refs/stash"] to a reasonable value to get traditional auto-expiration behaviour back * Longstanding latency issue with bash completion script has been addressed. This will need to be backmerged to 'maint' later. * pager.<cmd> configuration variable can be used to enable/disable the default paging behaviour per command. * "git-add -i" has a new action 'e/dit' to allow you edit the patch hunk manually. * git-am records the original tip of the branch in ORIG_HEAD before it starts applying patches. * git-apply can handle a patch that touches the same path more than once much better than before. * git-apply can be told not to trust the line counts recorded in the input patch but recount, with the new --recount option. * git-apply can be told to apply a patch to a path deeper than what the patch records with --directory option. * git-archive can be told to omit certain paths from its output using export-ignore attributes. * git-archive uses the zlib default compression level when creating zip archive. * git-archive's command line options --exec and --remote can take their parameters as separate command line arguments, similar to other commands. IOW, both "--exec=path" and "--exec path" are now supported. * With -v option, git-branch describes the remote tracking statistics similar to the way git-checkout reports by how many commits your branch is ahead/behind. * git-branch's --contains option used to always require a commit parameter to limit the branches with; it now defaults to list branches that contains HEAD if this parameter is omitted. * git-branch's --merged and --no-merged option used to always limit the branches relative to the HEAD, but they can now take an optional commit argument that is used in place of HEAD. * git-bundle can read the revision arguments from the standard input. * git-cherry-pick can replay a root commit now. * git-clone can clone from a remote whose URL would be rewritten by configuration stored in $HOME/.gitconfig now. * "git-clone --mirror" is a handy way to set up a bare mirror repository. * git-cvsserver learned to respond to "cvs co -c". * git-diff --check now checks leftover merge conflict markers. * "git-diff -p" learned to grab a better hunk header lines in BibTex, Pascal/Delphi, and Ruby files and also pays attention to chapter and part boundary in TeX documents. * When remote side used to have branch 'foo' and git-fetch finds that now it has branch 'foo/bar', it refuses to lose the existing remote tracking branch and its reflog. The error message has been improved to suggest pruning the remote if the user wants to proceed and get the latest set of branches from the remote, including such 'foo/bar'. * fast-export learned to export and import marks file; this can be used to interface with fast-import incrementally. * fast-import and fast-export learned to export and import gitlinks. * "gitk" left background process behind after being asked to dig very deep history and the user killed the UI; the process is killed when the UI goes away now. * git-rebase records the original tip of branch in ORIG_HEAD before it is rewound. * "git rerere" can be told to update the index with auto-reused resolution with rerere.autoupdate configuration variable. * git-rev-parse learned $commit^! and $commit^@ notations used in "log" family. These notations are available in gitk as well, because the gitk command internally uses rev-parse to interpret its arguments. * git-rev-list learned --children option to show child commits it encountered during the traversal, instead of showing parent commits. * git-send-mail can talk not just over SSL but over TLS now. * git-shortlog honors custom output format specified with "--pretty=format:". * "git-stash save" learned --keep-index option. This lets you stash away the local changes and bring the changes staged in the index to your working tree for examination and testing. * git-stash also learned branch subcommand to create a new branch out of stashed changes. * git-status gives the remote tracking statistics similar to the way git-checkout reports by how many commits your branch is ahead/behind. * "git-svn dcommit" is now aware of auto-props setting the subversion user has. * You can tell "git status -u" to even more aggressively omit checking untracked files with --untracked-files=no. * Original SHA-1 value for "update-ref -d" is optional now. * Error codes from gitweb are made more descriptive where possible, rather than "403 forbidden" as we used to issue everywhere. (internal) * git-merge has been reimplemented in C. +------------------+ |Fixes since v1.5.6| +------------------+ All of the fixes in v1.5.6 maintenance series are included in this release, unless otherwise noted. * git-clone ignored its -u option; the fix needs to be backported to 'maint'; * git-mv used to lose the distinction between changes that are staged and that are only in the working tree, by staging both in the index after moving such a path. * "git-rebase -i -p" rewrote the parents to wrong ones when amending (either edit or squash) was involved, and did not work correctly when fast forwarding. |
||
minskim
|
ecd1f604dc |
Remove a patch that disables the Mac OS X GUI application; now PLIST has
entries to handle that. |
||
minskim
|
46d9d4eee3 |
Enable the GUI application for Mac OS X when the scmgit-gui option
is given. While here, add clean to PRIVILEGED_STATES; otherwise, an unprivileged user cannot remove the Mac OS X GUI application with "make clean". |
||
minskim
|
95198f9965 |
scmgit-base builds an extra GUI application on Mac OS X. Add its files
to PLIST. Bump PKGREVISION. |
||
tonio
|
b0bb264da8 | Disable the installation of Git Gui.app under Darwin | ||
bjs
|
702a0280c5 |
Update to version 1.5.6.4. The base package now depends on devel/p5-Error;
this ensures that git never has to install its own copy, thereby avoiding future conflicts with devel/p5-Error. Plus, the pkgsrc version is newer. While here, set PKG_SYSCONFSUBDIR=git and explicitly specify sysconfdir in CONFIGURE_ARGS. Remove trailing slash from GITCOREDIR. Long list of changes since 1.5.6: Fixes since v1.5.6.3 -------------------- * Various commands could overflow its internal buffer on a platform with small PATH_MAX value in a repository that has contents with long pathnames. * There wasn't a way to make --pretty=format:%<> specifiers to honor .mailmap name rewriting for authors and committers. Now you can with %aN and %cN. * Bash completion wasted too many cycles; this has been optimized to be usable again. * Bash completion lost ref part when completing something like "git show pu:Makefile". * "git-cvsserver" did not clean up its temporary working area after annotate request. * "git-daemon" called syslog() from its signal handler, which was a no-no. * "git-fetch" into an empty repository used to remind that the fetch will be huge by saying "no common commits", but this was an unnecessary noise; it is already known by the user anyway. * "git-http-fetch" would have segfaulted when pack idx file retrieved from the other side was corrupt. * "git-index-pack" used too much memory when dealing with a deep delta chain. * "git-mailinfo" (hence "git-am") did not correctly handle in-body [PATCH] line to override the commit title taken from the mail Subject header. * "git-rebase -i -p" lost parents that are not involved in the history being rewritten. * "git-rm" lost track of where the index file was when GIT_DIR was specified as a relative path. * "git-rev-list --quiet" was not quiet as advertised. Contains other various documentation fixes. Fixes since v1.5.6.2 -------------------- * Setting core.sharerepository to traditional "true" value was supposed to make the repository group writable but should not affect permission for others. However, since 1.5.6, it was broken to drop permission for others when umask is 022, making the repository unreadable by others. * Setting GIT_TRACE will report spawning of external process via run_command(). * Using an object with very deep delta chain pinned memory needed for extracting intermediate base objects unnecessarily long, leading to excess memory usage. * Bash completion script did not notice '--' marker on the command line and tried the relatively slow "ref completion" even when completing arguments after one. * Registering a non-empty blob racily and then truncating the working tree file for it confused "racy-git avoidance" logic into thinking that the path is now unchanged. * The section that describes attributes related to git-archive were placed in a wrong place in the gitattributes(5) manual page. * "git am" was not helpful to the users when it detected that the committer information is not set up properly yet. * "git clone" had a leftover debugging fprintf(). * "git clone -q" was not quiet enough as it used to and gave object count and progress reports. * "git clone" marked downloaded packfile with .keep; this could be a good thing if the remote side is well packed but otherwise not, especially for a project that is not really big. * "git daemon" used to call syslog() from a signal handler, which could raise signals of its own but generally is not reentrant. This was fixed by restructuring the code to report syslog() after the handler returns. * When "git push" tries to remove a remote ref, and corresponding tracking ref is missing, we used to report error (i.e. failure to remove something that does not exist). * "git mailinfo" (hence "git am") did not handle commit log messages in a MIME multipart mail correctly. Futureproof ----------- * "git-shell" accepts requests without a dash between "git" and subcommand name (e.g. "git upload-pack") which the newer client will start to make sometime in the future. Fixes since v1.5.6.1 -------------------- * "git clone" from a remote that is named with url.insteadOf setting in $HOME/.gitconfig did not work well. * "git describe --long --tags" segfaulted when the described revision was tagged with a lightweight tag. * "git diff --check" did not report the result via its exit status reliably. * When remote side used to have branch 'foo' and git-fetch finds that now it has branch 'foo/bar', it refuses to lose the existing remote tracking branch and its reflog. The error message has been improved to suggest pruning the remote if the user wants to proceed and get the latest set of branches from the remote, including such 'foo/bar'. * "git reset file" should mean the same thing as "git reset HEAD file", but we required disambiguating -- even when "file" is not ambiguous. * "git show" segfaulted when an annotated tag that points at another annotated tag was given to it. * Optimization for a large import via "git-svn" introduced in v1.5.6 had a serious memory and temporary file leak, which made it unusable for moderately large import. * "git-svn" mangled remote nickname used in the configuration file unnecessarily. Fixes since v1.5.6 ------------------ * Last minute change broke loose object creation on AIX. * (performance fix) We used to make $GIT_DIR absolute path early in the programs but keeping it relative to the current directory internally gives 1-3 per-cent performance boost. * bash completion knows the new --graph option to git-log family. * git-diff -c/--cc showed unnecessary "deletion" lines at the context boundary. * git-for-each-ref ignored %(object) and %(type) requests for tag objects. * git-merge usage had a typo. * Rebuilding of git-svn metainfo database did not take rewriteRoot option into account. * Running "git-rebase --continue/--skip/--abort" before starting a rebase gave nonsense error messages. |
||
bjs
|
15e8625bcd |
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. |
||
bjs
|
f01ab0a334 |
Update to version 1.5.5.1. No pkgsrc changes, this time.
GIT v1.5.5.1 Release Notes ========================== Fixes since v1.5.5 ------------------ * "git archive --prefix=$path/" mishandled gitattributes. * "git fetch -v" that fetches into FETCH_HEAD did not report the summary the same way as done for updating the tracking refs. * "git svn" misbehaved when the configuration file customized the "git log" output format using format.pretty. * "git submodule status" leaked an unnecessary error message. * "git log --date-order --topo-order" did not override the earlier date-order with topo-order as expected. * "git bisect good $this" did not check the validity of the revision given properly. * "url.<there>.insteadOf" did not work correctly. * "git clean" ran inside subdirectory behaved as if the directory was explicitly specified for removal by the end user from the top level. * "git bisect" from a detached head leaked an unnecessary error message. * "git bisect good $a $b" when $a is Ok but $b is bogus should have atomically failed before marking $a as good. * "git fmt-merge-msg" did not clean up leading empty lines from commit log messages like "git log" family does. * "git am" recorded a commit with empty Subject: line without complaining. * when given a commit log message whose first paragraph consists of multiple lines, "git rebase" squashed it into a single line. * "git remote add $bogus_name $url" did not complain properly. * Also comes with various documentation updates. |
||
xtraeme
|
2187568ded |
Add the 'scmgit-gui' option. If enabled, the GUI in Tcl/Tk will be
build, otherwise not. Use the PLIST_VARS stuff to handle the PLIST file. Enabled by default to respect previous behaviour. |
||
bjs
|
0fd77342e8 |
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. |
||
bjs
|
6e38660617 |
Update to v1.5.4.5.
GIT v1.5.4.5 Release Notes ========================== Fixes since v1.5.4.4 -------------------- * "git fetch there" when the URL information came from the Cogito style branches/there file did not update refs/heads/there (regression in 1.5.4). * Bogus refspec configuration such as "remote.there.fetch = =" were not detected as errors (regressionin 1.5.4). * You couldn't specify a custom editor whose path contains a whitespace via GIT_EDITOR (and core.editor). * The subdirectory filter to "git filter-branch" mishandled a history where the subdirectory becomes empty and then later becomes non-empty. * "git shortlog" gave an empty line if the original commit message was malformed (e.g. a botched import from foreign SCM). Now it finds the first non-empty line and uses it for better information. * When the user fails to give a revision parameter to "git svn", an error from the Perl interpreter was issued because the script lacked proper error checking. * After "git rebase" stopped due to conflicts, if the user played with "git reset" and friends, "git rebase --abort" failed to go back to the correct commit. * Additional work trees prepared with git-new-workdir (in contrib/) did not share git-svn metadata directory .git/svn with the original. * "git-merge-recursive" did not mark addition of the same path with different filemodes correctly as a conflict. * "gitweb" gave malformed URL when pathinfo stype paths are in use. * "-n" stands for "--no-tags" again for "git fetch". * "git format-patch" did not detect the need to add 8-bit MIME header when the user used format.header configuration. * "rev~" revision specifier used to mean "rev", which was inconsistent with how "rev^" worked. Now "rev~" is the same as "rev~1" (hence it also is the same as "rev^1"), and "rev~0" is the same as "rev^0" (i.e. it has to be a commit). * "git quiltimport" did not grok empty lines, lines in "file -pNNN" format to specify the prefix levels and lines with trailing comments. * "git rebase -m" triggered pre-commit verification, which made "rebase --continue" impossible. As usual, it also comes with many documentation fixes and clarifications. |
||
bjs
|
7a626ea1a2 |
Update to version 1.5.4.4. Fix warning on NetBSD with wrong type
being passed in struct to localtime_r (convert from timeval to timespec). GIT v1.5.4.4 Release Notes ========================== Fixes since v1.5.4.3 -------------------- * Building and installing with an overtight umask such as 077 made installed templates unreadable by others, while the rest of the install are done in a way that is friendly to umask 022. * "git cvsexportcommit -w $cvsdir" misbehaved when GIT_DIR is set to a relative directory. * "git http-push" had an invalid memory access that could lead it to segfault. * When "git rebase -i" gave control back to the user for a commit that is marked to be edited, it just said "modify it with commit --amend", without saying what to do to continue after modifying it. Give an explicit instruction to run "rebase --continue" to be more helpful. * "git send-email" in 1.5.4.3 issued a bogus empty In-Reply-To: header. * "git bisect" showed mysterious "won't bisect on seeked tree" error message. This was leftover from Cogito days to prevent "bisect" starting from a cg-seeked state. We still keep the Cogito safety, but running "git bisect start" when another bisect was in effect will clean up and start over. * "git push" with an explicit PATH to receive-pack did not quite work if receive-pack was not on usual PATH. We earlier fixed the same issue with "git fetch" and upload-pack, but somehow forgot to do so in the other direction. * git-gui's info dialog was not displayed correctly when the user tries to commit nothing (i.e. without staging anything). * "git revert" did not properly fail when attempting to run with a dirty index. * "git merge --no-commit --no-ff <other>" incorrectly made commits. * "git merge --squash --no-ff <other>", which is a nonsense combination of options, was not rejected. * "git ls-remote" and "git remote show" against an empty repository failed, instead of just giving an empty result (regression). * "git fast-import" did not handle a renamed path whose name needs to be quoted, due to a bug in unquote_c_style() function. * "git cvsexportcommit" was confused when multiple files with the same basename needed to be pushed out in the same commit. * "git daemon" did not send early errors to syslog. * "git log --merge" did not work well with --left-right option. * "git svn" promprted for client cert password every time it accessed the server. * The reset command in "git fast-import" data stream was documented to end with an optional LF, but it actually required one. * "git svn dcommit/rebase" did not honor --rewrite-root option. Also included are a handful documentation updates. |
||
bjs
|
b7bf9ef864 |
Update to 1.5.4.3. While here, change pkgsrc Makefiles to use the included
configure script. This not only makes our Makefiles more readable, but also performs various checks that were previously hard-coded, e.g. whether or not iconv's *char arguments are constified or not. We also no longer need the huge mess which checks for the asciidoc/xmlto versions in git-docs/Makefile. Also, misc. makefile fixes/stylistic changes and removal of Python dependencies. I don't see how they are needed. Python modules should be installed as seperate ${PKGPKGPREFIX}-scmgit packages. This was a somewhat radical change, so please report any problems. Changes since 1.5.4: * RPM spec used to pull in everything with 'git'. This has been changed so that 'git' package contains just the core parts, and we now supply 'git-all' metapackage to slurp in everything. This should match end user's expectation better. * When some refs failed to update, git-push reported "failure" which was unclear if some other refs were updated or all of them failed atomically (the answer is the former). Reworded the message to clarify this. * "git clone" from a repository whose HEAD was misconfigured did not set up the remote properly. Now it tries to do better. * Updated git-push documentation to clarify what "matching" means, in order to reduce user confusion. * Updated git-add documentation to clarify "add -u" operates in the current subdirectory you are in, just like other commands. * git-gui updates to work on OSX and Windows better. * The configuration parser was not prepared to see string valued variables misspelled as boolean and segfaulted. * Temporary files left behind due to interrupted object transfers were not cleaned up with "git prune". * "git config --unset" was confused when the unset variables were spelled with continuation lines in the config file. * The merge message detection in "git cvsimport" did not catch a message that began with "Merge...". * "git status" suggests "git rm --cached" for unstaging the earlier "git add" before the initial commit. * "git status" output was incorrect during a partial commit. * "git bisect" refused to start when the HEAD was detached. * "git bisect" allowed a wildcard character in the commit message expanded while writing its log file. * Manual pages were not formatted correctly with docbook xsl 1.72; added a workaround. * "git-commit -C $tag" used to work but rewrite in C done in 1.5.4 broke it. This was fixed in 1.5.4.1. * An entry in the .gitattributes file that names a pattern in a subdirectory of the directory it is in did not match correctly (e.g. pattern "b/*.c" in "a/.gitattributes" should match "a/b/foo.c" but it didn't). This was fixed in 1.5.4.1. * Customized color specification was parsed incorrectly when numeric color values are used. This was fixed in 1.5.4.1. * http transport misbehaved when linked with curl-gnutls. * "git-commit -C $tag" used to work but rewrite in C done in 1.5.4 broke it. * An entry in the .gitattributes file that names a pattern in a subdirectory of the directory it is in did not match correctly (e.g. pattern "b/*.c" in "a/.gitattributes" should match "a/b/foo.c" but it didn't). * Customized color specification was parsed incorrectly when numeric color values are used. This was fixed in 1.5.4.1. |
||
tnn
|
40c910b11d |
Patch up some rather ... odd use of $HOME:
Instead of setting prefix=$(HOME) and HOME=${PREFIX}, just set prefix=$(PREFIX) directly. |
||
bjs
|
b43895ffb5 |
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. |
||
tnn
|
ad6ceadd25 |
Per the process outlined in revbump(1), perform a recursive revbump
on packages that are affected by the switch from the openssl 0.9.7 branch to the 0.9.8 branch. ok jlam@ |
||
bjs
|
4bcdf3fe12 |
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. |