All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Erik Werner <martinerikwerner@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.0.0-rc4
Date: Wed, 21 May 2014 12:02:45 +0200	[thread overview]
Message-ID: <20140521100245.GB2201@mule> (raw)
In-Reply-To: <xmqqr43oq8q5.fsf@gitster.dls.corp.google.com>

On Tue, May 20, 2014 at 05:24:50PM -0700, Junio C Hamano wrote:
(...)
>  * "git reset" learned the "-N" option, which does not reset the index
>    fully for paths the index knows about but the tree-ish the command
>    resets to does not (these paths are kept as intend-to-add entries).

I find it quite hard to parse this sentance. Maybe something like:

    which keeps paths as intent-to-add entries if they are currently
    staged, but not present in the tree-ish being reset to.

would be clearer (I hope I've actually managed to understand it..)?

(...)
>  * Commands that take pathspecs on the command line misbehaved when
>    the pathspec is given as an absolute pathname (which is a
>    practice not particularly encouraged) that points at a symbolic
>    link in the working tree.
>    (merge later 655ee9e mw/symlinks to maint.)

In order to include the latest cleanup to this patchset:
"setup: fix windows path buffer over-stepping"
this should be 6127ff6 instead. Sorry if it's unneeded to note, but just
wanted to make sure :)

--
Martin Erik Werner <martinerikwerner@gmail.com>

  parent reply	other threads:[~2014-05-21 10:02 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 [this message]
2014-05-21 17:03   ` Junio C Hamano
2014-05-21 21:30 ` Richard Hansen
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=20140521100245.GB2201@mule \
    --to=martinerikwerner@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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.