From: Sverre Rabbelier <srabbelier@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git 1.7.1.rc0
Date: Wed, 7 Apr 2010 10:25:45 -0500 [thread overview]
Message-ID: <t2pfabb9a1e1004070825q9df8a76aofdff7a2f460aee6d@mail.gmail.com> (raw)
In-Reply-To: <7vmxxfe20g.fsf@alter.siamese.dyndns.org>
Heya,
On Wed, Apr 7, 2010 at 10:05, Junio C Hamano <gitster@pobox.com> wrote:
> * Conflict markers that lead the common ancestor in diff3-style output
> now has a label, which hopefully would help third-party tools that
s/has/have/
> * "git notes" command has been rewritten in C and learned quite a
> many commands and features
Not sure if that is grammatically correct.
> * "git add frotz/nitfol" did not complain when the entire frotz/ directory
> was ignored.
Glad that this is fixed now :).
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-04-07 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 15:05 [ANNOUNCE] Git 1.7.1.rc0 Junio C Hamano
2010-04-07 15:25 ` Sverre Rabbelier [this message]
2010-04-07 20:57 ` [PATCH] fix typos and grammar in 1.7.1 draft release notes Jeff King
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=t2pfabb9a1e1004070825q9df8a76aofdff7a2f460aee6d@mail.gmail.com \
--to=srabbelier@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 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).