Git

Greetings, This is an initial announcement of SCuMD, a pure java git sshd daemon. The source is at git://github.com/gaffo/scumd. The impetus behind SCuMD is to provide a highly configurable git daemon which can authenticate and authorize off ... [More] of flat files, databases, LDAP, web services, or any other resource you can think of. SCuMD's other goal is to remove the need to serve off of normal sshd which some find to be a security risk on the open Internet. Currently SCuMD supports LDAP as the authentication module but coding other modules is quite simple. I would welcome any feedback including a better name. SCuMD stands for SCM Daemon. Thanks, Mike Gaffney -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html [Less]

Hi, Thanks to massive contributions from various people the project GitSharp has progressed very fast. GitSharp now counts about 17753 lines of code, the jgit.lib snapshot we are porting from counts 24588 lines. This means that roughly 72% of the ... [More] porting work are done! About two months ago, when I announced the project on this list only about 25% had been done. There is also still much testing work to do [Less]

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

The latest feature release GIT 1.6.4 is available at the usual places: http://www.kernel.org/pub/software/scm/git/ git-1.6.4.tar.{gz,bz2} (source tarball) git-htmldocs-1.6.4.tar.{gz,bz2} (preformatted docs) ... [More] git-manpages-1.6.4.tar.{gz,bz2} (preformatted docs) The RPM binary packages for a few architectures are found in: RPMS/$arch/git-*-1.6.4-1.fc9.$arch.rpm (RPM) GIT v1.6.4 Release Notes ======================== 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. 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. 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. Updates since v1.6.3 -------------------- (subsystems) * gitweb Perl style clean-up. * 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. (portability) * 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. (performance) * 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. (usability, bells and whistles) * "git add --edit" lets users edit the whole patch text to fine-tune what is added to the index. * "git am" accepts StGIT series file as its input. * "git bisect skip" skips to a more randomly chosen place in the hope to avoid testing a commit that is too close to a commit that is already known to be untestable. * "git cvsexportcommit" learned -k option to stop CVS keywords expansion * "git fast-export" learned to handle history simplification more gracefully. * "git fast-export" learned an option --tag-of-filtered-object to handle dangling tags resulting from history simplification more usefully. * "git grep" learned -p option to show the location of the match using the same context hunk marker "git diff" uses. * https transport can optionally be told that the used client certificate is password protected, in which case it asks the password only once. * "git imap-send" is IPv6 aware. * "git log --graph" draws graphs more compactly by using horizontal lines when able. * "git log --decorate" shows shorter refnames by stripping well-known refs/* prefix. * "git push $name" honors remote.$name.pushurl if present before using remote.$name.url. In other words, the URL used for fetching and pushing can be different. * "git send-email" understands quoted aliases in .mailrc files (might have to be backported to 1.6.3.X). * "git send-email" can fetch the sender address from the configuration variable "sendmail.from" (and "sendmail..from"). * "git show-branch" can color its output. * "add" and "update" subcommands to "git submodule" learned --reference option to use local clone with references. * "git submodule update" learned --rebase option to update checked out submodules by rebasing the local changes. * "gitweb" can optionally use gravatar to adorn author/committer names. (developers) * A major part of the "git bisect" wrapper has moved to C. * Formatting with the new version of AsciiDoc 8.4.1 is now supported. Fixes since v1.6.3 ------------------ All of the fixes in v1.6.3.X maintenance series are included in this release, unless otherwise noted. Here are fixes that this release has, but have not been backported to v1.6.3.X series. * "git diff-tree -r -t" used to omit new or removed directories from the output. df533f3 (diff-tree -r -t: include added/removed directories in the output, 2009-06-13) may need to be cherry-picked to backport this fix. * The way Git.pm sets up a Repository object was not friendly to callers that chdir around. It now internally records the repository location as an absolute path when autodetected. * Removing a section with "git config --remove-section", when its section header has a variable definition on the same line, lost that variable definition. * "git rebase -p --onto" used to always leave side branches of a merge intact, even when both branches are subject to rewriting. * "git repack" used to faithfully follow grafts and considered true parents recorded in the commit object unreachable from the commit. After such a repacking, you cannot remove grafts without corrupting the repository. * "git send-email" did not detect erroneous loops in alias expansion. -- 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.3.4 is available at the usual places: http://www.kernel.org/pub/software/scm/git/ git-1.6.3.4.tar.{gz,bz2} (source tarball) git-htmldocs-1.6.3.4.tar.{gz,bz2} (preformatted docs) ... [More] git-manpages-1.6.3.4.tar.{gz,bz2} (preformatted docs) The RPM binary packages for a few architectures are found in: RPMS/$arch/git-*-1.6.3.4-1.fc9.$arch.rpm (RPM) This is primarily to flush accumulated fixes on the 'maint' branch before going forward with 1.6.4 series. GIT v1.6.3.4 Release Notes ========================== Fixes since v1.6.3.3 -------------------- * "git add --no-ignore-errors" did not override configured add.ignore-errors configuration. * "git apply --whitespace=fix" did not fix trailing whitespace on an incomplete line. * "git branch" opened too many commit objects unnecessarily. * "git checkout -f $commit" with a path that is a file (or a symlink) in the work tree to a commit that has a directory at the path issued an unnecessary error message. * "git diff -c/--cc" was very inefficient in coalescing the removed lines shared between parents. * "git diff -c/--cc" showed removed lines at the beginning of a file incorrectly. * "git remote show nickname" did not honor configured remote.nickname.uploadpack when inspecting the branches at the remote. * "git request-pull" when talking to the terminal for a preview showed some of the output in the pager. * "git request-pull start nickname [end]" did not honor configured remote.nickname.uploadpack when it ran git-ls-remote against the remote repository to learn the current tip of branches. Includes other documentation updates and minor fixes. ---------------------------------------------------------------- Changes since v1.6.3.3 are as follows: Brandon Casey (2): refs.c: release file descriptor on error return sha1_name.c: avoid unnecessary strbuf_release Chris Frey (1): git-remote: fix missing .uploadpack usage for show command Clemens Buchacher (1): fetch: do not create ref from empty name Giuseppe Bilotta (1): gitweb/README: fix AliasMatch in example Johannes Sixt (2): t3700-add: add a POSIXPERM prerequisite to a new test Makefile: git.o depends on library headers Junio C Hamano (9): request-pull: really disable pager checkout -f: deal with a D/F conflict entry correctly combine-diff.c: fix performance problem when folding common deleted lines diff --cc: a lost line at the beginning of the file is shown incorrectly do_one_ref(): null_sha1 check is not about broken ref SunOS grep does not understand -C nor -e Fix severe breakage in "git-apply --whitespace=fix" t8005: Nobody writes Russian in shift_jis GIT 1.6.3.4 Linus Torvalds (3): git branch: fix performance problem git branch: avoid unnecessary object lookups git branch: clean up detached branch handling Matthias Andree (1): Fix export_marks() error handling. Michal Marek (1): request-pull: really really disable pager Miklos Vajna (1): git-submodule documentation: fix foreach example René Scharfe (1): attr: plug minor memory leak Roel Kluin (1): fread does not return negative on error SZEDER Gábor (1): Trailing whitespace and no newline fix Sitaram Chamarty (1): Documentation: update description of shell aliases Stephen Boyd (2): add: allow configurations to be overriden by command line config.txt: document add.ignore-errors Thadeu Lima de Souza Cascardo (1): Makes some cleanup/review in gittutorial Thomas Rast (2): Test git archive --remote Test grep --and/--or/--not Tom Grennan (1): request-pull: allow ls-remote to notice remote.$nickname.uploadpack -- 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.4.rc3 is available at the usual places for testing: http://www.kernel.org/pub/software/scm/git/ git-1.6.4.rc3.tar.{gz,bz2} (source tarball) git-htmldocs-1.6.4.rc3.tar.{gz,bz2} (preformatted docs) ... [More] git-manpages-1.6.4.rc3.tar.{gz,bz2} (preformatted docs) The RPM binary packages for a few architectures are found in: testing/git-*-1.6.4.rc3-1.fc9.$arch.rpm (RPM) An embarrassing and serious bug in "git am/apply" that was in 1.6.4-rc2 has been squashed, and this snapshot should be both safe to use and is expected to be the last -rc before the real thing. Please give it a good beating. GIT v1.6.4 Release Notes (draft) ================================ 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. 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. 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. Updates since v1.6.3 -------------------- (subsystems) * gitweb Perl style clean-up. * 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. (portability) * 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. (performance) * 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. (usability, bells and whistles) * "git add --edit" lets users edit the whole patch text to fine-tune what is added to the index. * "git am" accepts StGIT series file as its input. * "git bisect skip" skips to a more randomly chosen place in the hope to avoid testing a commit that is too close to a commit that is already known to be untestable. * "git cvsexportcommit" learned -k option to stop CVS keywords expansion * "git grep" learned -p option to show the location of the match using the same context hunk marker "git diff" uses. * https transport can optionally be told that the used client certificate is password protected, in which case it asks the password only once. * "git imap-send" is IPv6 aware. * "git log --graph" draws graphs more compactly by using horizontal lines when able. * "git log --decorate" shows shorter refnames by stripping well-known refs/* prefix. * "git push $name" honors remote.$name.pushurl if present before using remote.$name.url. In other words, the URL used for fetching and pushing can be different. * "git send-email" understands quoted aliases in .mailrc files (might have to be backported to 1.6.3.X). * "git send-email" can fetch the sender address from the configuration variable "sendmail.from" (and "sendmail..from"). * "git show-branch" can color its output. * "add" and "update" subcommands to "git submodule" learned --reference option to use local clone with references. * "git submodule update" learned --rebase option to update checked out submodules by rebasing the local changes. * "gitweb" can optionally use gravatar to adorn author/committer names. (developers) * A major part of the "git bisect" wrapper has moved to C. * Formatting with the new version of AsciiDoc 8.4.1 is now supported. Fixes since v1.6.3 ------------------ All of the fixes in v1.6.3.X maintenance series are included in this release, unless otherwise noted. Here are fixes that this release has, but have not been backported to v1.6.3.X series. * "git diff-tree -r -t" used to omit new or removed directories from the output. df533f3 (diff-tree -r -t: include added/removed directories in the output, 2009-06-13) may need to be cherry-picked to backport this fix. * The way Git.pm sets up a Repository object was not friendly to callers that chdir around. It now internally records the repository location as an absolute path when autodetected. * Removing a section with "git config --remove-section", when its section header has a variable definition on the same line, lost that variable definition. * "git repack" used to faithfully follow grafts and considered true parents recorded in the commit object unreachable from the commit. After such a repacking, you cannot remove grafts without corrupting the repository. * "git send-email" did not detect erroneous loops in alias expansion. --- exec >/var/tmp/1 echo O=$(git describe master) O=v1.6.4-rc2-31-g2ceb639 git shortlog --no-merges $O..master ^maint -- 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.4-rc2 is available at the usual places for testing: http://www.kernel.org/pub/software/scm/git/ git-1.6.4.rc2.tar.{gz,bz2} (source tarball) git-htmldocs-1.6.4.rc2.tar.{gz,bz2} (preformatted docs) ... [More] git-manpages-1.6.4.rc2.tar.{gz,bz2} (preformatted docs) The RPM binary packages for a few architectures are found in: testing/git-*-1.6.4.rc2-1.fc9.$arch.rpm (RPM) The changes since -rc1 are all small fixes and documentation updates; we are in a very good shape to expect 1.6.4 final by the end of the month. GIT v1.6.4 Release Notes (draft) ================================ 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. 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. 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. Updates since v1.6.3 -------------------- (subsystems) * gitweb Perl style clean-up. * 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, etc. (portability) * 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 "ISO8850-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. (performance) * 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. (usability, bells and whistles) * "git add --edit" lets users edit the whole patch text to fine-tune what is added to the index. * "git am" accepts StGIT series file as its input. * "git bisect skip" skips to a more randomly chosen place in the hope to avoid testing a commit that is too close to a commit that is already known to be untestable. * "git cvsexportcommit" learned -k option to stop CVS keywords expansion * "git grep" learned -p option to show the location of the match using the same context hunk marker "git diff" uses. * https transport can optionally be told that the used client certificate is password protected, in which case it asks the password only once. * "git imap-send" is IPv6 aware. * "git log --graph" draws graphs more compactly by using horizonal lines when able. * "git log --decorate" shows shorter refnames by stripping well-known refs/* prefix. * "git push $name" honors remote.$name.pushurl if present before using remote.$name.url. In other words, the URL used for fetching and pushing can be different. * "git send-email" understands quoted aliases in .mailrc files (might have to be backported to 1.6.3.X). * "git send-email" can fetch the sender address from the configuration variable "sendmail.from" (and "sendmail..from"). * "git show-branch" can color its output. * "add" and "update" subcommands to "git submodule" learned --reference option to use local clone with references. * "git submodule update" learned --rebase option to update checked out submodules by rebasing the local changes. * "gitweb" can optionally use gravatar to adorn author/committer names. (developers) * A major part of the "git bisect" wrapper has moved to C. Fixes since v1.6.3 ------------------ All of the fixes in v1.6.3.X maintenance series are included in this release, unless otherwise noted. Here are fixes that this release has, but have not been backported to v1.6.3.X series. * "git diff-tree -r -t" used to omit new or removed directories from the output. df533f3 (diff-tree -r -t: include added/removed directories in the output, 2009-06-13) may need to be cherry-picked to backport this fix. * The way Git.pm sets up a Repository object was not friendly to callers that chdir around. It now internally records the repository location as an absolute path when autodetected. --- exec >/var/tmp/1 echo O=$(git describe master) O=v1.6.4-rc1-7-gbba0fd2 git shortlog --no-merges $O..master ^maint ---------------------------------------------------------------- Changes since v1.6.4-rc1 are as follows: Brandon Casey (4): refs.c: release file descriptor on error return sha1_name.c: avoid unnecessary strbuf_release configure.ac: rework/fix the NEEDS_RESOLV and NEEDS_LIBGEN tests configure.ac: properly unset NEEDS_SSL_WITH_CRYPTO when sha1 func is missing Eric Wong (2): git svn: rename tests that had conflicting numbers git svn: fix reparenting when ugly http(s) URLs are used Junio C Hamano (5): checkout -f: deal with a D/F conflict entry correctly push: do not give big warning when no preference is configured Updates to draft release notes to 1.6.4 combine-diff.c: fix performance problem when folding common deleted lines diff --cc: a lost line at the beginning of the file is shown incorrectly Martin Koegler (1): git stash: modernize use of "dashed" git-XXX calls Michael J Gruber (1): t4202-log.sh: Test git log --no-walk sort order Mike Ralphson (1): cvsexportcommit: reorder tests to quiet intermittent failure Pierre Habouzit (4): janitor: use NULL and not 0 for pointers. refactor: use bitsizeof() instead of 8 * sizeof() janitor: add DIV_ROUND_UP and use it. janitor: useless checks before free SZEDER Gábor (1): Trailing whitespace and no newline fix Yann Dirson (2): List send-email config options in config.txt. Improve doc for format-patch threading options. -- 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]

To reduce the pain with the merging of my config changes (for various software) with upstream’s new defaults, I came up with a small program to track the default config files in a Git branch. With things set up, the update and the merge become a ... [More] matter of: % ./update-defaults (or whatever you’ll call your script) % git merge defaults (or whatever you’ll call the defaults branch) The program is generic, of course – I’ve already found other uses for it[1]. The README: http://github.com/ion1/update-base-branch#readme How I use the program in real life – examples of what the update-defaults script mentioned above could look like: http://github.com/ion1/update-base-branch/tree/master/examples#browser Release tarball: http://johan.kiviniemi.name/software/update-base-branch/ A demonstration: using the program to update the user config for the Awesome window manager: http://www.youtube.com/watch?v=RQ3CqJ4jM90&fmt=18 [1] If there is no public VCS repository for a piece of software and you want to maintain/send patches, use update-base-branch to track the contents of the latest released tarball and merge that branch with your ‘master’. -- Jοhan Kiviniemi -- 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 15/07/09, Junio C Hamano wrote: > A release candidate GIT 1.6.4.rc1 is available at the usual places > for testing: > > http://www.kernel.org/pub/software/scm/git/ Could you push into kernel.org, please? -- Nicolas Sebrecht -- ... [More] 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.4.rc1 is available at the usual places for testing: http://www.kernel.org/pub/software/scm/git/ git-1.6.4.rc1.tar.{gz,bz2} (source tarball) git-htmldocs-1.6.4.rc1.tar.{gz,bz2} (preformatted docs) ... [More] git-manpages-1.6.4.rc1.tar.{gz,bz2} (preformatted docs) The RPM binary packages for a few architectures are found in: testing/git-*-1.6.4.rc1-1.fc9.$arch.rpm (RPM) GIT v1.6.4 Release Notes (draft) ================================ 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. 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. 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. When the user does not tell "git push" what to push, it has always pushed matching refs. For some people it is unexpected, and a new configuration variable push.default has been introduced to allow changing a different default behaviour. To advertise the new feature, a big warning is issued if this is not configured and a git push without arguments is attempted. Side note: we might want to tone this down, as it does not seem likely for us to change the default behaviour when this option is not set. Updates since v1.6.3 -------------------- (subsystems) * gitweb Perl style clean-up. * git-svn updates, including a new --authors-prog option to map author names by invoking an external program. (portability) * We feed iconv with "UTF-8" instead of "utf8"; the former is understood more widely. (performance) (usability, bells and whistles) * "git add --edit" lets users edit the whole patch text to fine-tune what is added to the index. * "git log --graph" draws graphs more compactly by using horizonal lines when able. * "git log --decorate" shows shorter refnames by stripping well-known refs/* prefix. * "git send-email" understands quoted aliases in .mailrc files (might have to be backported to 1.6.3.X). * "git send-email" can fetch the sender address from the configuration variable "sendmail.from" (and "sendmail..from"). * "git show-branch" can color its output. * "add" and "update" subcommands to "git submodule" learned --reference option to use local clone with references. (developers) * A major part of the "git bisect" wrapper has moved to C. Fixes since v1.6.3 ------------------ All of the fixes in v1.6.3.X maintenance series are included in this release, unless otherwise noted. Here are fixes that this release has, but have not been backported to v1.6.3.X series. * The way Git.pm sets up a Repository object was not friendly to callers that chdir around. It now internally records the repository location as an absolute path when autodetected. -- 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]