git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: What's in git.git (Mar 2009, #03; Fri, 06)
Date: Fri, 06 Mar 2009 00:26:34 -0800	[thread overview]
Message-ID: <7vocwft5tx.fsf@gitster.siamese.dyndns.org> (raw)

Quite a many topics that have been scheduled for 'master' for some time
have all graduated.  With this pace we may be able to have a very short
cycle for a change before 1.6.3 final ;-).

* The 'master' branch has these since the last announcement.

Arjen Laarhoven (2):
  Clean up use of ANSI color sequences
  builtin-branch.c: Rename branch category color names

Deskin Miller (1):
  add -i: revisit hunk on editor failure

Elijah Newren (1):
  Ensure proper setup of git_dir for git-hash-object

Felipe Contreras (3):
  config: Add new option to open an editor.
  git config: codestyle cleanups
  Add tests for git log --pretty, --format and --oneline.

Finn Arne Gangstad (1):
  Support "\" in non-wildcard exclusion entries

Jay Soffian (6):
  builtin-branch: improve output when displaying remote branches
  send-email: allow send-email to run outside a repo
  send-email: handle multiple Cc addresses when reading mbox message
  send-email: --suppress-cc improvements
  send-email: don't create temporary compose file until it is needed
  send-email: add --confirm option and configuration setting

Jeff King (4):
  valgrind: ignore ldso and more libz errors
  branch: clean up repeated strlen
  add basic branch display tests
  never fallback relative times to absolute

Jeremy White (2):
  Enable setting attach as the default in .gitconfig for git-format-patch.
  imap.preformattedHTML to tell Thunderbird to send non-flowed text

Johannes Schindelin (11):
  Add valgrind support in test scripts
  Valgrind support: check for more than just programming errors
  test-lib.sh: optionally output to test-results/$TEST.out, too
  t/Makefile: provide a 'valgrind' target
  Add a script to coalesce the valgrind outputs
  Tests: let --valgrind imply --verbose and --tee
  test-lib: avoid assuming that templates/ are in the GIT_EXEC_PATH
  valgrind: do not require valgrind 3.4.0 or newer
  Avoid segfault with 'git branch' when the HEAD is detached
  git config: trivial cleanup for editor action
  MinGW: 64-bit file offsets

John Tapsell (1):
  Documentation - More examples for git bisect

Junio C Hamano (4):
  git-blame: refactor code to emit "porcelain format" output
  blame: show "previous" information in --porcelain/--incremental format
  git-add -i/-p: learn to unwrap C-quoted paths
  Draft release notes: Carry forward the warning for behaviour changes

Marius Storm-Olsen (2):
  Add bare repository indicator for __git_ps1
  Fixup: Add bare repository indicator for __git_ps1

Nanako Shiraishi (3):
  Add --format that is a synonym to --pretty
  Give short-hands to --pretty=tformat:%formatstring
  Add --oneline that is a synonym to "--pretty=oneline --abbrev-commit"

SZEDER Gábor (1):
  rerere: remove duplicated functions

Sverre Rabbelier (1):
  Teach rebase to rebase even if upstream is up to date

Ted Pavlic (4):
  completion: For consistency, change "git rev-parse" to __gitdir calls
  completion: Use consistent if [...] convention, not "test"
  completion: Better __git_ps1 support when not in working directory
  completion: More fixes to prevent unbound variable errors

Teemu Likonen (1):
  bash completion: add --format= and --oneline options for "git log"

             reply	other threads:[~2009-03-06  8:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06  8:26 Junio C Hamano [this message]
2009-03-06  9:44 ` What's in git.git (Mar 2009, #03; Fri, 06) Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vocwft5tx.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).