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 (Nov 2008, #04; Wed, 26)
Date: Wed, 26 Nov 2008 16:28:03 -0800	[thread overview]
Message-ID: <7v8wr6c8rw.fsf@gitster.siamese.dyndns.org> (raw)

I suspect many people especially the ones in the US will be in vacation
mode and not near their keyboards til next week, but here is an update.

There are a few 'maint' material cooking in 'next' and v1.6.0.5 should be
tagged at the end of the month.

At around the same time I am hoping majority of topics cooking in 'next'
tonight can be in 'master' and we can tagl v1.6.1-rc1.

* The 'maint' branch has these fixes since the last announcement.

Bryan Drewery (1):
  Fix misleading wording for git-cherry-pick

Junio C Hamano (3):
  builtin-ls-files.c: coding style fix.
  Teach ls-files --with-tree=<tree> to work with options other than -c
  Teach "git diff" to honour --[no-]ext-diff

Matt McCutchen (1):
  config.txt: alphabetize configuration sections

Stefan Naewe (1):
  request-pull: make usage string match manpage


* The 'master' branch has these since the last announcement
  in addition to the above.

Alex Riesen (2):
  Fix handle leak in sha1_file/unpack_objects if there were damaged object
    data
  Fix t4030-diff-textconv.sh

Alexander Gavrilov (6):
  git-gui: Implement system-wide configuration handling.
  git-gui: Fix the after callback execution in rescan.
  git-gui: Add a Tools menu for arbitrary commands.
  git-gui: Allow Tools request arguments from the user.
  git-gui: Implement automatic rescan after Tool execution.
  git-gui: Fix the search bar destruction handler.

Alexandre Julliard (9):
  git.el: Improve error handling for commits.
  git.el: Remove the env parameter in git-call-process and
    git-call-process-string.
  git.el: Simplify handling of merge heads in the commit log-edit buffer.
  git.el: Properly handle merge commits in git-amend-commit.
  git.el: Fix git-amend-commit to support amending an initial commit.
  git.el: Never clear the status buffer, only update the files.
  git.el: Add an insert file command.
  git.el: Add possibility to mark files directly in
    git-update-status-files.
  git.el: Allow to commit even if there are no marked files.

Brandon Casey (1):
  repack: only unpack-unreachable if we are deleting redundant packs

Cheng Renquan (1):
  git-remote: match usage string with the manual pages

Christian Couder (2):
  Documentation: user-manual: add information about "git help" at the
    beginning
  Documentation: tutorial: add information about "git help" at the
    beginning

Giuseppe Bilotta (1):
  git-gui: try to provide a window icon under X

Jeff King (3):
  define empty tree sha1 as a macro
  wt-status: refactor initial commit printing
  status: show "-v" diff even for initial commit

Jim Meyering (1):
  xdiff-interface.c: remove 10 duplicated lines

Joey Hess (1):
  sha1_file: avoid bogus "file exists" error message

Junio C Hamano (1):
  builtin-remote.c: plug a small memory leak in
    get_one_remote_for_updates()

Linus Torvalds (1):
  Fix machine-parseability of 'git log --source'

Marcel Koeppen (1):
  t9129-git-svn-i18n-commitencoding: Make compare_svn_head_with()
    compatible with OSX sed

Mark Burton (2):
  Documentation: rev-list-options.txt: added --branches, --tags &
    --remotes.
  git-commit.txt - mention that files listed on the command line must be
    known to git.

Miklos Vajna (3):
  builtin-branch: use strbuf in delete_branches()
  builtin-branch: use strbuf in fill_tracking_info()
  builtin-branch: use strbuf in rename_branch()

Shawn O. Pearce (1):
  Update the po template

Trent Piepho (1):
  send-email: Fix Pine address book parsing

                 reply	other threads:[~2008-11-27  0:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=7v8wr6c8rw.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).