Next | Query returned 118 messages, browsing 41 to 50 | Previous

History of commit frequency

CVS Commit History:


   2012-03-26 09:28:18 by Filip Hajny | Files touched by this commit (1)
Log message:
Fix inet_ntop/inet_pton conflict on SunOS and ABI=64.
   2012-03-09 18:02:15 by Adam Ciarcinski | Files touched by this commit (7)
Log message:
Changes 1.7.9.3:
* "git p4" (in contrib/) submit the changes to a wrong place when the
  "--use-client-spec" option is set.
* The config.mak.autogen generated by optional autoconf support tried
  to link the binary with -lintl even when libintl.h is missing from
  the system.
* When the filter driver exits before reading the content before the
  main git process writes the contents to be filtered to the pipe to
  it, the latter could be killed with SIGPIPE instead of ignoring
  such an event as an error.
* "git add --refresh <pathspec>" used to warn about unmerged paths
  outside the given pathspec.
* The bulk check-in codepath in "git add" streamed contents that
  needs smudge/clean filters without running them, instead of punting
  and delegating to the codepath to run filters after slurping
  everything to core.
* "git branch --with $that" assumed incorrectly that the user will never
  ask the question with nonsense value in $that.
* "git bundle create" produced a corrupt bundle file upon seeing
  commits with excessively long subject line.
* When a remote helper exits before reading the blank line from the
  main git process to signal the end of commands, the latter could be
  killed with SIGPIPE. Instead we should ignore such event as a
  non-error.
* The commit log template given with "git merge --edit" did not have
  a short instructive text like what "git commit" gives.
* "git rev-list --verify-objects -q" omitted the extra verification
  it needs to do over "git rev-list --objects -q" by mistake.
* "gitweb" used to drop warnings in the log file when \ 
"heads" view is
  accessed in a repository whose HEAD does not point at a valid
  branch.
* An invalid regular expression pattern given by an end user made
  "gitweb" to return garbled response.
   2012-02-28 18:13:09 by Greg Troxel | Files touched by this commit (1)
Log message:
Add mail-related p5 packages.

Add MIME::Base64 and Authen::SASL for git-send-email to resolve
PR pkg/46109.  Adds mere hundreds of K to a package that 'pkg_info -s'
says is hundreds of MB.
   2012-02-23 16:16:24 by Greg Troxel | Files touched by this commit (2) | Package updated
Log message:
Update to 1.7.9.2.

Fixes since v1.7.9.1
--------------------

 * Bash completion script (in contrib/) did not like a pattern that
   begins with a dash to be passed to __git_ps1 helper function.

 * Adaptation of the bash completion script (in contrib/) for zsh
   incorrectly listed all subcommands when "git \ 
<TAB><TAB>" was given
   to ask for list of porcelain subcommands.

 * The build procedure for profile-directed optimized binary was not
   working very well.

 * Some systems need to explicitly link -lcharset to get locale_charset().

 * t5541 ignored user-supplied port number used for HTTP server testing.

 * The error message emitted when we see an empty loose object was
   not phrased correctly.

 * The code to ask for password did not fall back to the terminal
   input when GIT_ASKPASS is set but does not work (e.g. lack of X
   with GUI askpass helper).

 * We failed to give the true terminal width to any subcommand when
   they are invoked with the pager, i.e. "git -p cmd".

 * map_user() was not rewriting its output correctly, which resulted
   in the user visible symptom that "git blame -e" sometimes showed
   excess '>' at the end of email addresses.

 * "git checkout -b" did not allow switching out of an unborn branch.

 * When you have both .../foo and .../foo.git, "git clone .../foo" did not
   favor the former but the latter.

 * "git commit" refused to create a commit when entries added with
   "add -N" remained in the index, without telling Git what their content
   in the next commit should be. We should have created the commit without
   these paths.

 * "git diff --stat" said "files", "insertions", \ 
and "deletions" even
   when it is showing one "file", one "insertion" or one \ 
"deletion".

 * The output from "git diff --stat" for two paths that have the same
   amount of changes showed graph bars of different length due to the
   way we handled rounding errors.

 * "git grep" did not pay attention to -diff (hence -binary) attribute.

 * The transport programs (fetch, push, clone)ignored --no-progress
   and showed progress when sending their output to a terminal.

 * Sometimes error status detected by a check in an earlier phase of
   "git receive-pack" (the other end of "git push") was lost \ 
by later
   checks, resulting in false indication of success.

 * "git rev-list --verify" sometimes skipped verification depending on
   the phase of the moon, which dates back to 1.7.8.x series.

 * Search box in "gitweb" did not accept non-ASCII characters correctly.

 * Search interface of "gitweb" did not show multiple matches in the \ 
same file
   correctly.

Also contains minor fixes and documentation updates.
   2012-02-17 14:54:02 by Hans Rosenfeld | Files touched by this commit (1)
Log message:
Fix build on SunOS.
   2012-02-14 23:46:36 by Greg Troxel | Files touched by this commit (3)
Log message:
Update to 1.7.9.1.

(This is a bugfix release relative to 1.7.9.)
   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-21 11:16:44 by OBATA Akio | Files touched by this commit (1)
Log message:
add a missing entry.
   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.
   2012-01-20 08:03:11 by Takahiro Kambe | Files touched by this commit (1) | Package updated
Log message:
Make sure to update distinfo.

Next | Query returned 118 messages, browsing 41 to 50 | Previous