Next | Query returned 34 messages, browsing 11 to 20 | Previous

History of commit frequency

CVS Commit History:


   2012-09-28 19:34:18 by Alan Barrett | Files touched by this commit (1)
Log message:
Perl is needed at build time.  So add these lines to the Makefile
USE_TOOLS+=             perl:run
CONFIGURE_ARGS+=       --with-perl=${PERL5:Q}
   2012-09-04 14:17:12 by Adam Ciarcinski | Files touched by this commit (6) | Package updated
Log message:
Changes 1.7.12:
UI, Workflows & Features
 * Git can be told to normalize pathnames it read from readdir(3) and
   all arguments it got from the command line into precomposed UTF-8
   (assuming that they come as decomposed UTF-8), in order to work
   around issues on Mac OS.
   I think there still are other places that need conversion
   (e.g. paths that are read from stdin for some commands), but this
   should be a good first step in the right direction.
 * Per-user $HOME/.gitconfig file can optionally be stored in
   $HOME/.config/git/config instead, which is in line with XDG.
 * The value of core.attributesfile and core.excludesfile default to
   $HOME/.config/git/attributes and $HOME/.config/git/ignore respectively
   when these files exist.
 * Logic to disambiguate abbreviated object names have been taught to
   take advantage of object types that are expected in the context,
   e.g. XXXXXX in the "git describe" output v1.2.3-gXXXXXX must be a
   commit object, not a blob nor a tree.  This will help us prolong
   the lifetime of abbreviated object names.
 * "git apply" learned to wiggle the base version and perform three-way
   merge when a patch does not exactly apply to the version you have.
 * Scripted Porcelain writers now have access to the credential API via
   the "git credential" plumbing command.
 * "git help" used to always default to "man" format even on \ 
platforms
   where "man" viewer is not widely available.
 * "git clone --local $path" started its life as an experiment to
   optionally use link/copy when cloning a repository on the disk, but
   we didn't deprecate it after we made the option a no-op to always
   use the optimization.  The command learned "--no-local" option to
   turn this off, as a more explicit alternative over use of file://
   URL.
 * "git fetch" and friends used to say "remote side hung up
   unexpectedly" when they failed to get response they expect from the
   other side, but one common reason why they don't get expected
   response is that the remote repository does not exist or cannot be
   read. The error message in this case was updated to give better
   hints to the user.
 * "git help -w $cmd" can show HTML version of documentation for
   "git-$cmd" by setting help.htmlpath to somewhere other than the
   default location where the build procedure installs them locally;
   the variable can even point at a http:// URL.
 * "git rebase [-i] --root $tip" can now be used to rewrite all the
   history leading to "$tip" down to the root commit.
 * "git rebase -i" learned "-x <cmd>" to insert \ 
"exec <cmd>" after
   each commit in the resulting history.
 * "git status" gives finer classification to various states of paths
   in conflicted state and offer advice messages in its output.
 * "git submodule" learned to deal with nested submodule structure
   where a module is contained within a module whose origin is
   specified as a relative URL to its superproject's origin.
 * A rather heavy-ish "git completion" script has been split to create
   a separate "git prompting" script, to help lazy-autoloading of the
   completion part while making prompting part always available.
 * "gitweb" pays attention to various forms of credits that are
   similar to "Signed-off-by:" lines in the commit objects and
   highlights them accordingly.
   2012-07-09 16:30:50 by Adam Ciarcinski | Files touched by this commit (7) | Package updated
Log message:
Changes 1.7.11.1:
* The cross links in the HTML version of manual pages were broken.
Also contains minor typofixes and documentation updates.

Changes 1.7.11:
UI, Workflows & Features
 * A new mode for push, "simple", which is a cross between \ 
"current"
   and "upstream", has been introduced. "git push" without \ 
any refspec
   will push the current branch out to the same name at the remote
   repository only when it is set to track the branch with the same
   name over there.  The plan is to make this mode the new default
   value when push.default is not configured.
 * A couple of commands learned the "--column" option to produce
   columnar output.
 * A third-party tool "git subtree" is distributed in contrib/
 * A remote helper that acts as a proxy and caches ssl session for the
   https:// transport is added to the contrib/ area.
 * Error messages given when @{u} is used for a branch without its
   upstream configured have been clarified.
 * Even with the "-q"uiet option, "checkout" used to report \ 
setting up
   tracking.  Also "branch" learned the "-q"uiet option to \ 
squelch
   informational message.
 * Your build platform may support hardlinks but you may prefer not to
   use them, e.g. when installing to DESTDIR to make a tarball and
   untarring on a filesystem that has poor support for hardlinks.
   There is a Makefile option NO_INSTALL_HARDLINKS for you.
 * The smart-http backend used to always override GIT_COMMITTER_*
   variables with REMOTE_USER and REMOTE_ADDR, but these variables are
   now preserved when set.
 * "git am" learned the "--include" option, which is an \ 
opposite of
   existing the "--exclude" option.
 * When "git am -3" needs to fall back to an application of the patch
   to a synthesized preimage followed by a 3-way merge, the paths that
   needed such treatment are now reported to the end user, so that the
   result in them can be eyeballed with extra care.
 * The output from "diff/log --stat" used to always allocate 4 columns
   to show the number of modified lines, but not anymore.
 * "git difftool" learned the "--dir-diff" option to spawn \ 
external
   diff tools that can compare two directory hierarchies at a time
   after populating two temporary directories, instead of running an
   instance of the external tool once per a file pair.
 * The "fmt-merge-msg" command learned to list the primary contributors
   involved in the side topic you are merging in a comment in the merge
   commit template.
 * "git rebase" learned to optionally keep commits that do not
   introduce any change in the original history.
 * "git push --recurse-submodules" learned to optionally look into the
   histories of submodules bound to the superproject and push them
   out.
 * A 'snapshot' request to "gitweb" honors If-Modified-Since: header,
   based on the commit date.
 * "gitweb" learned to highlight the patch it outputs even more.
   2012-02-06 14:11:35 by Adam Ciarcinski | Files touched by this commit (7) | Package updated
Log message:
Changes 1.7.9:
* gitk updates accumulated since early 2011.
* git-gui updated to 0.16.0.
* git-p4 (in contrib/) updates.
* Git uses gettext to translate its most common interface messages
  into the user's language if translations are available and the
  locale is appropriately set. Distributors can drop new PO files
  in po/ to add new translations.
* The code to handle username/password for HTTP transactions used in
  "git push" & "git fetch" learned to talk \ 
"credential API" to
  external programs to cache or store them, to allow integration with
  platform native keychain mechanisms.
* The input prompts in the terminal use our own getpass() replacement
  when possible. HTTP transactions used to ask for the username without
  echoing back what was typed, but with this change you will see it as
  you type.
* The internals of "revert/cherry-pick" have been tweaked to prepare
  building more generic "sequencer" on top of the implementation that
  drives them.
* "git rev-parse FETCH_HEAD" after "git fetch" without specifying
  what to fetch from the command line will now show the commit that
  would be merged if the command were "git pull".
* "git add" learned to stream large files directly into a packfile
  instead of writing them into individual loose object files.
* "git checkout -B <current branch> <elsewhere>" is a more \ 
intuitive
  way to spell "git reset --keep <elsewhere>".
* "git checkout" and "git merge" learned \ 
"--no-overwrite-ignore" option
  to tell Git that untracked and ignored files are not expendable.
* "git commit --amend" learned "--no-edit" option to say that the
  user is amending the tree being recorded, without updating the
  commit log message.
* "git commit" and "git reset" re-learned the optimization \ 
to prime
  the cache-tree information in the index, which makes it faster to
  write a tree object out after the index entries are updated.
* "git commit" detects and rejects an attempt to stuff NUL byte in
  the commit log message.
* "git commit" learned "-S" to GPG-sign the commit; this can \ 
be shown
  with the "--show-signature" option to "git log".
* fsck and prune are relatively lengthy operations that still go
  silent while making the end-user wait. They learned to give progress
  output like other slow operations.
* The set of built-in function-header patterns for various languages
  knows MATLAB.
* "git log --format='<format>'" learned new %g[nNeE] specifiers to
  show information from the reflog entries when walking the reflog
  (i.e. with "-g").
* "git pull" can be used to fetch and merge an annotated/signed tag,
  instead of the tip of a topic branch. The GPG signature from the
  signed tag is recorded in the resulting merge commit for later
  auditing.
* "git log" learned "--show-signature" option to show the \ 
signed tag
  that was merged that is embedded in the merge commit. It also can
  show the signature made on the commit with "git commit -S".
* "git branch --edit-description" can be used to add descriptive text
  to explain what a topic branch is about.
* "git fmt-merge-msg" learned to take the branch description into
  account when preparing a merge summary that "git merge" records
  when merging a local branch.
* "git request-pull" has been updated to convey more information
  useful for integrators to decide if a topic is worth merging and
  what is pulled is indeed what the requestor asked to pull,
  including:
  - the tip of the branch being requested to be merged;
  - the branch description describing what the topic is about;
  - the contents of the annotated tag, when requesting to pull a tag.
* "git pull" learned to notice 'pull.rebase' configuration variable,
  which serves as a global fallback for setting 'branch.<name>.rebase'
  configuration variable per branch.
* "git tag" learned "--cleanup" option to control how the \ 
whitespaces
  and empty lines in tag message are cleaned up.
* "gitweb" learned to show side-by-side diff.
   2012-01-20 16:43:38 by Adam Ciarcinski | Files touched by this commit (4) | Package updated
Log message:
Changes 1.7.8.4:
* The code to look up attributes for paths reused entries from a wrong
  directory when two paths in question are in adjacent directories and
  the name of the one directory is a prefix of the other.
* A wildcard that matches deeper hierarchy given to the "diff-index" \ 
command,
  e.g. "git diff-index HEAD -- '*.txt'", incorrectly reported additions of
  matching files even when there is no change.
* When producing a "thin pack" (primarily used in bundles and smart
  HTTP transfers) out of a fully packed repository, we unnecessarily
  avoided sending recent objects as a delta against objects we know
  the other side has.
* "git send-email" did not properly treat sendemail.multiedit as a
  boolean (e.g. setting it to "false" did not turn it off).
* Also contains minor fixes and documentation updates.
   2011-10-11 14:01:25 by Adam Ciarcinski | Files touched by this commit (6) | Package updated
Log message:
Changes 1.7.7:
* The scripting part of the codebase is getting prepared for i18n/l10n.
* Interix, Cygwin and Minix ports got updated.
* Various updates to git-p4 (in contrib/), fast-import, and git-svn.
* Gitweb learned to read from /etc/gitweb-common.conf when it exists,
  before reading from gitweb_config.perl or from /etc/gitweb.conf
* Various codepaths that invoked zlib deflate/inflate assumed that these
  functions can compress or uncompress more than 4GB data in one call on
  platforms with 64-bit long, which has been corrected.
* Git now recognizes loose objects written by other implementations that
  use a non-standard window size for zlib deflation (e.g. Agit running on
  Android with 4kb window). We used to reject anything that was not
  deflated with 32kb window.
* Interaction between the use of pager and coloring of the output has
  been improved, especially when a command that is not built-in was
  involved.
* "git am" learned to pass the "--exclude=<path>" \ 
option through to underlying
  "git apply".
* You can now feed many empty lines before feeding an mbox file to "git \ 
am".
* "git archive" can be told to pass the output to gzip compression and
  produce "archive.tar.gz".
* "git bisect" can be used in a bare repository (provided that the test
  you perform per each iteration does not need a working tree, of course).
* The length of abbreviated object names in "git branch -v" output
  now honors the core.abbrev configuration variable.
* "git check-attr" can take relative paths from the command line.
* "git check-attr" learned an "--all" option to list the \ 
attributes for a
  given path.
* "git checkout" (both the code to update the files upon checking out a
  different branch and the code to checkout a specific set of files) learned
  to stream the data from object store when possible, without having to
  read the entire contents of a file into memory first. An earlier round
  of this code that is not in any released version had a large leak but
  now it has been plugged.
* "git clone" can now take a "--config key=value" option to \ 
set the
  repository configuration options that affect the initial checkout.
* "git commit <paths>..." now lets you feed relative pathspecs that
  refer to outside your current subdirectory.
* "git diff --stat" learned a --stat-count option to limit the output of
  a diffstat report.
* "git diff" learned a "--histogram" option to use a \ 
different diff
  generation machinery stolen from jgit, which might give better performance.
* "git diff" had a weird worst case behaviour that can be triggered
  when comparing files with potentially many places that could match.
* "git fetch", "git push" and friends no longer show connection
  errors for addresses that couldn't be connected to when at least one
  address succeeds (this is arguably a regression but a deliberate one).
* "git grep" learned "--break" and "--heading" \ 
options, to let users mimic
  the output format of "ack".
* "git grep" learned a "-W" option that shows wider context \ 
using the same
  logic used by "git diff" to determine the hunk header.
* Invoking the low-level "git http-fetch" without "-a" \ 
option (which
  git itself never did---normal users should not have to worry about
  this) is now deprecated.
* The "--decorate" option to "git log" and its family learned to
  highlight grafted and replaced commits.
* "git rebase master topci" no longer spews usage hints after giving
  the "fatal: no such branch: topci" error message.
* The recursive merge strategy implementation got a fairly large
  fix for many corner cases that may rarely happen in real world
  projects (it has been verified that none of the 16000+ merges in
  the Linux kernel history back to v2.6.12 is affected with the
  corner case bugs this update fixes).
* "git stash" learned an "--include-untracked option".
* "git submodule update" used to stop at the first error updating a
  submodule; it now goes on to update other submodules that can be
  updated, and reports the ones with errors at the end.
* "git push" can be told with the \ 
"--recurse-submodules=check" option to
  refuse pushing of the supermodule, if any of its submodules'
  commits hasn't been pushed out to their remotes.
* "git upload-pack" and "git receive-pack" learned to \ 
pretend that only a
  subset of the refs exist in a repository. This may help a site to
  put many tiny repositories into one repository (this would not be
  useful for larger repositories as repacking would be problematic).
* "git verify-pack" has been rewritten to use the \ 
"index-pack" machinery
  that is more efficient in reading objects in packfiles.
* test scripts for gitweb tried to run even when CGI-related perl modules
  are not installed; they now exit early when the latter are unavailable.
   2011-07-08 13:14:44 by Adam Ciarcinski | Files touched by this commit (4) | Package updated
Log message:
Changes 1.7.6:
* Various git-svn updates.
* Updates the way content tags are handled in gitweb.  Also adds
  a UI to choose common timezone for displaying the dates.
* Similar to branch names, tagnames that begin with "-" are now
  disallowed.
* Clean-up of the C part of i18n (but not l10n---please wait)
  continues.
* The scripting part of the codebase is getting prepared for i18n/l10n.
* Pushing and pulling from a repository with large number of refs that
  point to identical commits are optimized by not listing the same commit
  during the common ancestor negotiation exchange with the other side.
* Adding a file larger than core.bigfilethreshold (defaults to 1/2 Gig)
  using "git add" will send the contents straight to a packfile without
  having to hold it and its compressed representation both at the same
  time in memory.
* Processes spawned by "[alias] <name> = !process" in the \ 
configuration
  can inspect GIT_PREFIX environment variable to learn where in the
  working tree the original command was invoked.
* A magic pathspec ":/" tells a command that limits its operation to
  the current directory when ran from a subdirectory to work on the
  entire working tree. In general, ":/path/to/file" would be relative
  to the root of the working tree hierarchy.
  After "git reset --hard; edit Makefile; cd t/", "git add \ 
-u" would
  be a no-op, but "git add -u :/" would add the updated contents of
  the Makefile at the top level. If you want to name a path in the
  current subdirectory whose unusual name begins with ":/", you can
  name it by "./:/that/path" or by "\:/that/path".
* "git blame" learned "--abbrev[=<n>]" option to \ 
control the minimum
  number of hexdigits shown for commit object names.
* "git blame" learned "--line-porcelain" that is less \ 
efficient but is
  easier to parse.
* Aborting "git commit --interactive" discards updates to the index
  made during the interactive session.
* More...
   2011-04-06 16:08:28 by Adam Ciarcinski | Files touched by this commit (4) | Package updated
Log message:
Changes 1.7.4.3:
* "git apply" used to confuse lines updated by previous hunks as lines
  that existed before when applying a hunk, contributing misapplication
  of patches with offsets.
* "git branch --track" (and "git checkout --track --branch") \ 
used to
  allow setting up a random non-branch that does not make sense to follow
  as the "upstream".  The command correctly diagnoses it as an error.
* "git checkout $other_branch" silently removed untracked symbolic links
  in the working tree that are in the way in order to check out paths
  under it from the named branch.
* "git cvsimport" did not bail out immediately when the cvs server cannot
  be reached, spewing unnecessary error messages that complain about the
  server response that it never got.
* "git diff --quiet" did not work very well with the \ 
"--diff-filter" option.
* "git grep -n" lacked a long-hand synonym --line-number.
* "git stash apply" reported the result of its operation by running
  "git status" from the top-level of the working tree; it should (and
  now does) run it from the user's working directory.
   2011-03-11 10:28:40 by Adam Ciarcinski | Files touched by this commit (4)
Log message:
Changes 1.7.4.1:
* On Windows platform, the codepath to spawn a new child process forgot
  to first flush the output buffer.
* "git bundle" did not use OFS_DELTA encoding, making its output a few
  per-cent larger than necessarily.
* The option to tell "git clone" to recurse into the submodules was
  misspelled with an underscore "--recurse_submodules".
* "git diff --cached HEAD" before the first commit does what an end user
  would expect (namely, show what would be committed without further "git
  add").
* "git fast-import" didn't accept the command to ask for \ 
"notes" feature
  to be present in its input stream, even though it was capable of the
  feature.
* "git fsck" gave up scanning loose object files in directories with
  garbage files.
   2010-10-28 13:11:01 by Adam Ciarcinski | Files touched by this commit (1)
Log message:
Since HTML files are not installed, don't bother building them.

Next | Query returned 34 messages, browsing 11 to 20 | Previous