All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: What's in git.git (Dec 2008, #04; Mon, 29)
Date: Tue, 30 Dec 2008 13:03:46 -0800	[thread overview]
Message-ID: <7vbput1ikt.fsf@gitster.siamese.dyndns.org> (raw)

This is the last installment of "What's in" series of the year 2008.
Enjoy a happy new year break, everybody.

* The 'maint' branch has these fixes since v1.6.1.

Adeodato Simó (2):
  git-shortlog.txt: improve documentation about .mailmap files
  git-send-email.txt: move --format-patch paragraph to a proper location

Devin Doucette (1):
  gitweb: Fix export check in git_get_projects_list

Junio C Hamano (1):
  Prepare for v1.6.1.1 maintenance release

René Scharfe (7):
  daemon: handle freopen() failure
  daemon: cleanup: replace loop with if
  daemon: cleanup: factor out xstrdup_tolower()
  merge-file: handle freopen() failure
  pretty: factor out skip_empty_lines()
  pretty: factor out format_subject()
  pretty: support multiline subjects with format:

Shawn O. Pearce (1):
  describe: Avoid unnecessary warning when using --all

jidanni@jidanni.org (1):
  Documentation/diff-options.txt: unify options


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

Johannes Schindelin (1):
  Force t5302 to use a single thread

Junio C Hamano (2):
  Document "git-reset --merge"
  Start 1.6.2 cycle

Linus Torvalds (1):
  Add 'merge' mode to 'git reset'

Nicolas Pitre (2):
  autodetect number of CPUs by default when using threads
  pack-objects: don't use too many threads with few objects

Teemu Likonen (2):
  Fix the building of user-manual.texi and gitman.texi documents
  Fix the building of gitman.info document

                 reply	other threads:[~2008-12-30 21:05 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=7vbput1ikt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.