Git

The latest maintenance release Git 1.6.5.4 is available at the usual places: http://www.kernel.org/pub/software/scm/git/ git-1.6.5.4.tar.{gz,bz2} (source tarball) git-htmldocs-1.6.5.4.tar.{gz,bz2} (preformatted docs) ... [More] git-manpages-1.6.5.4.tar.{gz,bz2} (preformatted docs) The RPM binary packages for a few architectures are found in: RPMS/$arch/git-*-1.6.5.4-1.fc11.$arch.rpm (RPM) Contains some minor fixes that have been accumulated; all of them appear in the upcoming 1.6.6 release as well. This should fix the problem that man pages formatted on FC11 boxes are littered with "man.base.url.for.relative.link" strings reported earlier today. Git v1.6.5.4 Release Notes ========================== Fixes since v1.6.5.3 -------------------- * "git help" (without argument) used to check if you are in a directory under git control. There was no breakage in behaviour per-se, but this was unnecessary. * "git prune-packed" gave progress output even when its standard error is not connected to a terminal; this caused cron jobs that run it to produce crufts. * "git pack-objects --all-progress" is an option to ask progress output from write-object phase _if_ progress output were to be produced, and shouldn't have forced the progress output. * "git apply -p --directory=" did not work well for a non-default value of n. * "git merge foo HEAD" was misparsed as an old-style invocation of the command and produced a confusing error message. As it does not specify any other branch to merge, it shouldn't be mistaken as such. We will remove the old style "git merge HEAD ..." syntax in future versions, but not in this release, * "git merge -m ..." added the standard merge message on its own after user-supplied message, which should have overrided the standard one. Other minor documentation updates are included. ---------------------------------------------------------------- Changes since v1.6.5.3 are as follows: David Aguilar (1): help: Do not unnecessarily look for a repository David Soria Parra (1): Documentation: Document --branch option in git clone synopsis Greg Price (1): Documentation: undocument gc'd function graph_release() Jeff King (1): prune-packed: only show progress when stderr is a tty Junio C Hamano (7): builtin-apply.c: pay attention to -p when determining the name Do not misidentify "git merge foo HEAD" as an old-style invocation merge: do not add standard message when message is given with -m option Prepare for 1.6.5.4 Documentation/Makefile: allow man.base.url.for.relative.link to be set from Make Unconditionally set man.base.url.for.relative.links Git 1.6.5.4 Michael J Gruber (1): Documentation: Fix a few i.e./e.g. mix-ups Nicolas Pitre (1): pack-objects: split implications of --all-progress from progress activation Stephen Boyd (1): instaweb: restart server if already running -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]

A release candidate GIT 1.6.6.rc1 is available at the usual places for testing: http://www.kernel.org/pub/software/scm/git/ git-1.6.6.rc1.tar.{gz,bz2} (source tarball) git-htmldocs-1.6.6.rc1.tar.{gz,bz2} (preformatted docs) ... [More] git-manpages-1.6.6.rc1.tar.{gz,bz2} (preformatted docs) The RPM binary packages for a few architectures are found in: testing/git-*-1.6.6.rc1-1.fc11.$arch.rpm (RPM) Git v1.6.6 Release Notes (draft) ================================ 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, 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 use 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 tried very hard to avoid repeating that unpleasantness. For changes decided to be in 1.7.0, we have been much louder to strongly discourage such procrastination. If you have been using recent versions of git, you would have already seen warnings issued when you exercised features whose behaviour will change, with the instruction on how to keep the existing behaviour if you want to. You hopefully should be well prepared already. Of course, we have also given "this and that will change in 1.7.0; prepare yourselves" warnings in the release notes and announcement messages. 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 them 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 git-gui updates including new translations, wm states, etc. * 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. * The ancient "git merge HEAD ..." syntax will be removed in later versions of git. A warning is given and tells users to use the "git merge -m ..." instead. * "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 ", is now optional and inferred from the same way "git clone " does. * "git svn" learned to read SVN 1.5 and SVK merge tickets. * "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. * Enumeration of available merge strategies iterated over the list of commands in a wrong way, sometimes producing an incorrect result. Will backport by merging ed87465 (builtin-merge.c: call exclude_cmds() correctly., 2009-11-25). * "git format-patch revisions... -- path" issued an incorrect error message that suggested to use "--" on the command line when path does not exist in the current work tree (it is a separate matter if it makes sense to limit format-patch with pathspecs like that without using the --full-diff option). Will backport by merging 7e93d3b (format-patch: add test for parsing of "--", 2009-11-26). * "git shortlog" did not honor the "encoding" header embedded in the commit object like "git log" did. Will backport by merging 79f7ca0 (shortlog: respect commit encoding, 2009-11-25). ---------------------------------------------------------------- Changes since v1.6.6-rc0 are as follows: Avery Pennarun (1): builtin-merge.c: call exclude_cmds() correctly. Benjamin Kramer (1): Explicitly truncate bswap operand to uint32_t Bert Wesarg (2): Give the hunk comment its own color get_ref_states: strdup entries and free util in stale list Björn Gustavsson (11): Teach the --all option to 'git fetch' Teach the --multiple option to 'git fetch' Add the configuration option skipFetchAll Add missing test for 'git remote update --prune' Re-implement 'git remote update' using 'git fetch' Clarify and correct -z apply: apply works outside a repository apply: Format all options using back-quotes apply: Use the term "working tree" consistently Fix over-simplified documentation for 'git log -z' gitworkflows: Consistently back-quote git commands Brian Gernhardt (1): t/gitweb-lib: Split HTTP response with non-GNU sed Christian Couder (6): Documentation: add "Fighting regressions with git bisect" article replace: use a GIT_NO_REPLACE_OBJECTS env variable Documentation: fix typos and spelling in replace documentation Documentation: talk a little bit about GIT_NO_REPLACE_OBJECTS bisect: simplify calling visualizer using '--bisect' option Documentation: update descriptions of revision options related to '--bisect' David Aguilar (1): help: Do not unnecessarily look for a repository David Soria Parra (1): Documentation: Document --branch option in git clone synopsis Erick Mattos (1): commit -c/-C/--amend: reset timestamp and authorship to committer with --reset-author Felipe Contreras (3): format-patch: fix parsing of "--" on the command line format-patch: add test for parsing of "--" send-email: automatic envelope sender Horst H. von Brand (1): git-pull.sh: Fix call to git-merge for new command format Jakub Narebski (10): gitweb: Add optional "time to generate page" info in footer gitweb: Incremental blame (using JavaScript) gitweb: Colorize 'blame_incremental' view during processing gitweb: Create links leading to 'blame_incremental' using JavaScript gitweb: Minify gitweb.js if JSMIN is defined t/gitweb-lib.sh: Split gitweb output into headers and body gitweb: Document current snapshot rules via new tests gitweb.js: Harden setting blamed commit info in incremental blame gitweb: Make linking to actions requiring JavaScript a feature gitweb: Add link to other blame implementation in blame views Jay Soffian (4): remote: refactor some logic into get_stale_heads() teach warn_dangling_symref to take a FILE argument builtin-fetch: add --prune option builtin-fetch: add --dry-run option Jeff King (1): prune-packed: only show progress when stderr is a tty Johannes Sixt (2): t4014-format-patch: do not assume 'test' is available as non-builtin Add a notice that only certain functions can print color escape codes Jonathan Nieder (1): Makefile: do not clean arm directory Junio C Hamano (19): mailinfo: -b option keeps [bracketed] strings that is not a [PATCH] marker Pretty-format: %[ -]x to tweak inter-item newlines read_revision_from_stdin(): use strbuf Teach --stdin option to "log" family setup_revisions(): do not call get_pathspec() too early Make --stdin option to "log" family read also pathspecs t9001: test --envelope-sender option of send-email Add trivial tests for --stdin option to log family Protect scripted Porcelains from GREP_OPTIONS insanity builtin-apply.c: pay attention to -p when determining the name Remove dead code from "git am" emit_line(): don't emit an empty followed by a newline Update draft release notes to 1.6.6 before merging topics for -rc1 git-merge: a deprecation notice of the ancient command line syntax Update draft release notes to 1.6.6 before -rc1 Do not misidentify "git merge foo HEAD" as an old-style invocation merge: do not add standard message when message is given with -m option Prepare for 1.6.5.4 Git 1.6.6-rc1 Mark Rada (2): gitweb: check given hash before trying to create snapshot gitweb: Smarter snapshot names Martin Storsjö (3): Disable CURLOPT_NOBODY before enabling CURLOPT_PUT and CURLOPT_POST Refactor winsock initialization into a separate function Enable support for IPv6 on MinGW Matthew Ogilvie (5): cvsserver doc: database generally can not be reproduced consistently config documentation: some configs are auto-set by git-init t2300: use documented technique to invoke git-sh-setup t3409 t4107 t7406 t9150: use dashless commands t/README: Document GIT_TEST_INSTALLED and GIT_TEST_EXEC_PATH Matthieu Moy (4): merge-recursive: point the user to commit when file would be overwritten. user-manual: Document that "git merge" doesn't like uncommited changes. merge-recursive: make the error-message generation an extern function builtin-merge: show user-friendly error messages for fast-forward too. Michael J Gruber (1): Documentation: Fix a few i.e./e.g. mix-ups Nanako Shiraishi (2): t1200: fix a timing dependent error prepare send-email for smoother change of --chain-reply-to default Nicolas Pitre (1): pack-objects: split implications of --all-progress from progress activation Ramsay Allan Jones (1): git-count-objects: Fix a disk-space under-estimate on Cygwin René Scharfe (2): strbuf_add_wrapped_text(): skip over colour codes mergetool--lib: simplify guess_merge_tool() Stephen Boyd (3): gitweb.js: fix null object exception in initials calculation instaweb: restart server if already running gitweb.js: fix padLeftStr() and its usage Tay Ray Chuan (1): remote-curl.c: fix rpc_out() Uwe Kleine-König (1): shortlog: respect commit encoding -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]

Hello, After a long time of silence, here is a brand new version of tig with changes that has accummulated since version 0.14.1. It mainly brings minor improvements for tweaking tig usage via keybindings and options. Thanks to everybody who ... [More] provided patches. What is tig? ------------ Tig is an ncurses-based text-mode interface for git. It functions mainly as a git repository browser, but can also assist in staging changes for commit at chunk level and act as a pager for output from various git commands. - Homepage: http://jonas.nitro.dk/tig/ - Manual: http://jonas.nitro.dk/tig/manual.html - Tarballs: http://jonas.nitro.dk/tig/releases/ - Git URL: git://repo.or.cz/tig.git - Gitweb: http://repo.or.cz/w/tig.git Release notes ------------- Incompatibilities: - Setting the cursor color no longer automatically sets the text to bold. The old 'lazy' behavior was a bug. - Remove check for git-repo-config, which was officially deprecated in git version 1.5.4. The configure script no longer depends on git being installed. Improvements: - Provide the manual as a man page named tigmanual(7). - Add ability to toggle between showing shorter dates (without time info) and relative dates. Use 'D' to toggle between date formats. - Show the active (instead of the default) keybindings in the help view. Furthermore, honor the keymap when suggesting actions in the help messages. - Add branch view for choosing which branch to display in the main view. Bound to 'H' by default. - Tree view: show entry to parent directory ('..') when running from subdirectory. - Tree view: sort entries by name, date or author. Toggling is bound to 'i' by default, with 'I' controlling whether or not to sort in ascending order. - Make height of the lower view in a split view configurable by setting the 'split-view-height' variable to a number or a percentage. Defaults to 2/3 of the total view height. - Allow multiple text attributes for color commands: color cursor white blue underline bold Bug fixes: - Blame view: fix loading of blame data when opened from the tree view and CWD is not the repo root. (Debian bug 540766) - Tree view: fix searching. Change summary -------------- The diffstat and log summary for changes made in this release. .gitignore | 1 + INSTALL | 40 +- Makefile | 13 +- NEWS | 39 ++ TODO | 3 - VERSION | 2 +- configure.ac | 7 - contrib/aspell.dict | 8 +- manual.txt | 249 ++++---- tig.1.txt | 2 +- tig.c | 1549 ++++++++++++++++++++++++++++++------------- tigmanual.7.txt | 20 + tigrc.5.txt | 365 +++++------ 13 files changed, 1497 insertions(+), 801 deletions(-) Giuseppe Bilotta (2): Fix previous/next with branch+main view Predefined external command: git commit Ingmar Vanhassel (1): Makefile: Fix typo in 157ebf54 Jeff King (1): Add missing NULL in blame_grep Jonas Fonseca (40): Add small cache for author names to reduce memory foot-print Reduce memory and startup time by storing author times as time_t Simplify searching in view lines by defining grep_text utility Define a tree_grep and fixing searching Make the granular allocators more customizable using macros Remove the need for alloc variables Define an allocator for run requests Update the current branch information when reloading all references Fix a potential problem with reading tokens larger then BUFSIZ Add primitive branch view Minor fix to always sort even if allocation fails in get_refs Use temporary variable in refs loop in main_draw Branch view: fix loading to handle when two branches have same commit Add support for sorting tree entries by name, date or author Add support for sorting branch entries by name, date and author Fix reloading of references to not cause access to freed memory Restore the branch view position after refreshing Add simple support for showing menues and use it for showing option menu Use menus with the commit subject to present selectable commit parents Fix memory allocation check in open_commit_parent_menu Manual: document that : jumps to the line number Remove macros which are only used for default option values Allow multiple text attributes for color commands Build with asciidoc-8.4.5 Show the active (instead of the default) keybindings in the help view Merge remote branch 'samb/short-dates' NEWS: Mention date-shorten feature Add support for displaying relative dates Fix draw_date to not format anything when time arg is NULL Fix loading of blame data when opened from the tree view NEWS: Improve bug fix description Update asciidoc table syntax to the one supported by version 8.4.4 tigmanual(7): provide the manual as a man page Remove build dependency on git from the configure script begin_update: simplify control flow run_io_dir: take dir argument run_io_rd_dir: obsolete by switching call sites to run_io_rd_dir io_open: take path as a vararg format Status view: special case revert of unmerged entries with no physical file tig-0.15 Samuel Bronson (1): Add an option (and toggle) for shortening the date column by skipping the time. Sebastian Harl (1): Fixed some uninitialized variable warnings Tilo Schwarz (1): Make height of split view configurable bill lam (1): Fix whitespace -- Jonas Fonseca -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]

codeBeamer MR is a new tool for teams working with Git, and striving for fast repository management and easy access control management. Setting up and maintaining ACL on top of Git is not trivial. With this web based tool, you can *save a lot of ... [More] boring and error-prone maintainenace work*, and spend your time rather with coding. FEATURES * Starts and close projects and repositories in just seconds * Project-, group-, and role-based administration across multiple repositories * ACL on directory level * SSH authentication * Lightweight wiki, issue tracking and project management facilities * Web based * Remote API PRICE? It is *free* (as in beer). No expiration. LEARN MORE & DOWNLOAD More details, screenshots and downloads: http://www.intland.com/products/cb-mr/overview.html -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]

http://tortoisegit.googlecode.com/files/TortoiseGit-1.2.1.0-32bit.msi http://tortoisegit.googlecode.com/files/TortoiseGit-1.2.1.0-64bit.msi = Release 1.2.1.0 = == Features ==

The latest maintenance release GIT 1.6.5.3 is available at the usual places: http://www.kernel.org/pub/software/scm/git/ git-1.6.5.3.tar.{gz,bz2} (source tarball) git-htmldocs-1.6.5.3.tar.{gz,bz2} (preformatted docs) ... [More] git-manpages-1.6.5.3.tar.{gz,bz2} (preformatted docs) The RPM binary packages for a few architectures are found in: RPMS/$arch/git-*-1.6.5.3-1.fc9.$arch.rpm (RPM) Git v1.6.5.3 Release Notes ========================== Fixes since v1.6.5.2 -------------------- * info/grafts file didn't ignore trailing CR at the end of lines. * Packages generated on newer FC were unreadable by older versions of RPM as the new default is to use stronger hash. * output from "git blame" was unreadable when the file ended in an incomplete line. * "git add -i/-p" didn't handle deletion of empty files correctly. * "git clone" takes up to two parameters, but did not complain when given more arguments than necessary and silently ignored them. * "git cvsimport" did not read files given as command line arguments correctly when it is run from a subdirectory. * "git diff --color-words -U0" didn't work correctly. * The handling of blank lines at the end of file by "git diff/apply --whitespace" was inconsistent with the other kinds of errors. They are now colored, warned against, and fixed the same way as others. * There was no way to allow blank lines at the end of file without allowing extra blanks at the end of lines. You can use blank-at-eof and blank-at-eol whitespace error class to specify them separately. The old trailing-space error class is now a short-hand to set both. * "-p" option to "git format-patch" was supposed to suppress diffstat generation, but it was broken since 1.6.1. * "git imap-send" did not compile cleanly with newer OpenSSL. * "git help -a" outside of a git repository was broken. * "git ls-files -i" was supposed to be inverse of "git ls-files" without -i with respect to exclude patterns, but it was broken since 1.6.5.2. * "git ls-remote" outside of a git repository over http was broken. * "git rebase -i" gave bogus error message when the command word was misspelled. * "git receive-pack" that is run in response to "git push" did not run garbage collection nor update-server-info, but in larger hosting sites, these almost always need to be run. To help site administrators, the command now runs "gc --auto" and "u-s-i" by setting receive.autogc and receive.updateserverinfo configuration variables, respectively. * Release notes spelled the package name with incorrect capitalization. * "gitweb" did not escape non-ascii characters correctly in the URL. * "gitweb" showed "patch" link even for merge commits. * "gitweb" showed incorrect links for blob line numbers in pathinfo mode. Other minor documentation updates are included. ---------------------------------------------------------------- Changes since v1.6.5.2 are as follows: Björn Gustavsson (1): git-clone.txt: Fix grammar and formatting Björn Steinbrink (1): pre-commit.sample: Diff against the empty tree when HEAD is invalid Clemens Buchacher (1): modernize fetch/merge/pull examples Daniel Barkalow (2): Require a struct remote in transport_get() Allow curl helper to work without a local repository Dmitry V. Levin (1): Makefile: add compat/bswap.h to LIB_H Gerrit Pape (1): help -i: properly error out if no info viewer can be found Gisle Aas (2): More precise description of 'git describe --abbrev' Fix documentation grammar typo Giuseppe Bilotta (1): gitweb: fix esc_param Jakub Narebski (1): gitweb: Do not show 'patch' link for merge commits Jan Krüger (1): rebase -i: more graceful handling of invalid commands Jari Aalto (3): Documentation/fetch-options.txt: order options alphabetically Documentation/git-pull.txt: Add subtitles above included option files Documentation/merge-options.txt: order options in alphabetical groups Jeff King (6): cvsimport: fix relative argument filenames push: always load default config add-interactive: handle deletion of empty files ls-files: unbreak "ls-files -i" push: fix typo in usage format-patch: make "-p" suppress diffstat Johannes Schindelin (3): blame: make sure that the last line ends in an LF help -a: do not unnecessarily look for a repository diff --color-words -U0: fix the location of hunk headers Jonathan Nieder (4): clone: detect extra arguments Add intermediate build products to .gitignore check-ref-format: update usage string merge: do not setup worktree twice Junio C Hamano (22): apply --whitespace=fix: fix handling of blank lines at the eof apply --whitespace=fix: detect new blank lines at eof correctly apply.c: split check_whitespace() into two apply --whitespace=warn/error: diagnose blank at EOF apply --whitespace: warn blank but not necessarily empty lines at EOF diff.c: the builtin_diff() deals with only two-file comparison diff --whitespace=warn/error: obey blank-at-eof diff --whitespace=warn/error: fix blank-at-eof check diff --color: color blank-at-eof core.whitespace: split trailing-space into blank-at-{eol,eof} diff --whitespace: fix blank lines at end diff.c: shuffling code around diff.c: split emit_line() from the first char and the rest of the line diff.c: emit_add_line() takes only the rest of the line diff -B: colour whitespace errors info/grafts: allow trailing whitespaces at the end of line gc --auto --quiet: make the notice a bit less verboase receive-pack: run "gc --auto --quiet" and optionally "update-server-info" clone: fix help on options diff --color-words: bit of clean-up check-ref-format -h: it does not know the --print option yet Git 1.6.5.3 Markus Heidelberg (1): t4034-diff-words: add a test for word diff without context Petr Baudis (1): gitweb: Fix blob linenr links in pathinfo mode Sebastian Schuberth (1): Do not try to remove directories when removing old links Stephen Boyd (1): git-add.txt: fix formatting of --patch section Thomas Rast (1): Quote ' as \(aq in manpages Todd Zullinger (1): Makefile: Ensure rpm packages can be read by older rpm versions Vietor Liu (1): imap-send.c: fix compiler warnings for OpenSSL 1.0 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]

Hello! I would like to announce Girocco-1.0, the first stable release of a universal Git project hosting infrastructure. You can get it at http://repo.or.cz/w/girocco.git You guessed right, Girocco is the software repo.or.cz runs at; however ... [More] , compared to the past, it's much cleaned up, cleanly packaged for easy re-deployment and fully configurable, thanks to sponsorship of Novartis and Novell. (Apologies for switching repo.or.cz to it and releasing it one year later than it should've been done.) Thus, you should be able to easily deploy a local Girocco instance at your site and configure it to do only what you want. Girocco allows both full push-based project hosting, or just mirroring and showing existing projects (either local or remote) - i.e. you can also use it just to collect scattered repositories of your developers and present them all at single place. The push-based hosting offers currently two models, chroot hosting and hooks-based permissions (for trusted environments) - it should be easy to add other models. This way, Girocco might present an interesting alternative to Gitorious for people who prefer mirroring over full project hosting, prefer then rawer gitweb interface ;-), like the repo.or.cz simple forking model or want to make use of the GitHub-like flexible commit notifications mechanism. (If you are actually going to deploy Girocco somewhere, it's good to tell me so that I can take it into account to e.g. provide upgrade paths for future Girocco changes.) If you are used to repo.or.cz, what's new in Girocco at the user's end? * Friendlier homepage. * Friendlier project/user management interface. * Friendlier mirror cloning process (you can see the progress in your browser). * Support for automatic Git mirroring of SVN repositories. * Support for new-commit notifications, both for push and mirror project modes: * Get a notification to specified mail address(es) * Get a notification by receiving a POST HTTP request with GitHub-compatible JSON payload * Have repo.or.cz send commit notifications to the CIA service [http://cia.vc/] * Much easier to contribute a change to Girocco if you are missing any feature on repo.or.cz! Well, have fun! -- Petr "Pasky" Baudis A lot of people have my books on their bookshelves. That's the problem, they need to read them. -- Don Knuth -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]

Just a quick note for those of you interested in running a smart-http server once Shawns series graduates from 'pu' - I don't use Apache and the provided git-http-backend CGI script only works with Apache currently (and only CGI-supporting servers in ... [More] general). In order to allow Git smart-http to work through a wider variety of servers, I wrote a Rack application that does the same things that git-http-backend does, in case CGI/Apache is not your particular bag of fun. Rack (http://rack.rubyforge.org/) is a Ruby webserver interface - you can write an application for it and it has a bunch of handlers for common webservers so you can deal with a middleware abstraction rather than a specific server implementation. This is nice because it means the Rack app I wrote that provides (hopefully) identical functionality to the git-http-backend script can run in the following webservers: * Just about anything that supports CGI or FCGI * Mongrel (and EventedMongrel and SwiftipliedMongrel) * WEBrick * SCGI * LiteSpeed * Thin * Ebb * Fuzed * Phusion Passenger (which is mod_rack for Apache and for nginx) * Unicorn You can also generate a WAR file from it (via the Warbler project and JRuby) that can be loaded into any Java application server (I tested it on Glassfish, but Tomcat, Websphere, JBoss, Jetty, etc should all work too). The project is here: http://github.com/schacon/grack I've tested it on a few servers, I'll try to test it on more and provide example setups for each. If you use it, please let me know how things go. Scott -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]

The latest maintenance release GIT 1.6.5.2 is available at the usual places: http://www.kernel.org/pub/software/scm/git/ git-1.6.5.2.tar.{gz,bz2} (source tarball) git-htmldocs-1.6.5.2.tar.{gz,bz2} (preformatted docs) ... [More] git-manpages-1.6.5.2.tar.{gz,bz2} (preformatted docs) The RPM binary packages for a few architectures are found in: RPMS/$arch/git-*-1.6.5.2-1.fc9.$arch.rpm (RPM) GIT v1.6.5.2 Release Notes ========================== Fixes since v1.6.5.1 -------------------- * Installation of templates triggered a bug in busybox when using tar implementation from it. * "git add -i" incorrectly ignored paths that are already in the index if they matched .gitignore patterns. * "git describe --always" should have produced some output even there were no tags in the repository, but it didn't. * "git ls-files" when showing tracked files incorrectly paid attention to the exclude patterns. Other minor documentation updates are included. ---------------------------------------------------------------- Changes since v1.6.5.1 are as follows: Andreas Schwab (1): Work around option parsing bug in the busybox tar implementation Carlos R. Mafra (1): Makefile: clean block-sha1/ directory instead of mozilla-sha1/ Jeff King (2): ls-files: excludes should not impact tracked files document push's new quiet option Joe Perches (1): git-send-email.perl: fold multiple entry "Cc:" and multiple single line "RCPT TO:"s Johannes Sixt (2): Remove a left-over file from t/t5100 Mark files in t/t5100 as UTF-8 Jonathan Nieder (1): Documentation: describe check-ref-format --branch Junio C Hamano (4): Fix incorrect error check while reading deflated pack data Do not fail "describe --always" in a tag-less repository Fix list of released versions in the toc document GIT 1.6.5.2 Markus Heidelberg (1): t7800-difftool: fix the effectless GIT_DIFFTOOL_PROMPT test Matt Kraai (1): Documentation/git-gc.txt: change "references" to "reference" Nanako Shiraishi (2): git push: remove incomplete options list from help text git push: say that --tag can't be used with --all or --mirror in help text Nasser Grainawi (1): Document `delta` attribute in "git help attributes". Pauli Virtanen (1): git-add--interactive: never skip files included in index -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]

BugTracker.NET is a free, open-source, GPL, ASP.NET bug tracking app. More info at http://ifdefined.com/bugtrackernet.html With the integration, if you do a commit like... git commit -a -m "123 fixed the bug" ...then the hook script will link up ... [More] the commit to bug 123. Here are screenshots of the Subversion integration, which looks pretty much like the git integration: http://ifdefined.com/doc_bug_tracker_subversion.html Feedback very welcome, good or bad. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]