git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Hansen <rhansen@bbn.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git v2.0.0-rc4
Date: Wed, 21 May 2014 17:30:45 -0400	[thread overview]
Message-ID: <537D1B05.6030209@bbn.com> (raw)
In-Reply-To: <xmqqr43oq8q5.fsf@gitster.dls.corp.google.com>

On 2014-05-20 20:24, Junio C Hamano wrote:
> Fixes since v1.9 series
> -----------------------
> 
> Unless otherwise noted, all the fixes since v1.9 in the maintenance
> track are contained in this release (see the maintenance releases'
> notes for details).
[...]
>
>  * The shell prompt script (in contrib/), when using the PROMPT_COMMAND
>    interface, used an unsafe construct when showing the branch name in
>    $PS1.
>    (merge 8976500 rh/prompt-pcmode-avoid-eval-on-refname later to maint).

That commit has been merged to maint and is in v1.9.3.

Also, 1e4119c (git-prompt.sh: don't assume the shell expands the value
of PS1) is a fix that is in v2.0.0-rc4 but not v1.9.x.  Maybe add
something like:

 * The shell prompt script (in contrib/), when using Zsh and the
   precmd() interface, printed ${__git_ps1_branch_name} in the prompt
   instead of the branch name (regression in v1.9.3).
   (merge 1e4119c rh/prompt-pcmode-avoid-eval-on-refname later to
   maint).

-Richard

  parent reply	other threads:[~2014-05-21 21:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21  0:24 [ANNOUNCE] Git v2.0.0-rc4 Junio C Hamano
2014-05-21  0:36 ` Felipe Contreras
2014-05-21  4:25   ` David Kastrup
2014-05-21 17:05   ` Junio C Hamano
2014-05-22  3:45     ` Felipe Contreras
2014-05-21 10:02 ` Martin Erik Werner
2014-05-21 17:03   ` Junio C Hamano
2014-05-21 21:30 ` Richard Hansen [this message]
2014-05-21 21:48   ` 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=537D1B05.6030209@bbn.com \
    --to=rhansen@bbn.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=linux-kernel@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).