git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duy Nguyen <pclouds@gmail.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Charles Bailey <charles@hashpling.org>,
	Git List <git@vger.kernel.org>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v2 2/2] grep: fix grepping for "intent to add" files
Date: Wed, 22 Jun 2016 18:01:44 +0200	[thread overview]
Message-ID: <CACsJy8Biaowr-XoaJgOCXjDGre==CzeSyADftCAdzxFHoxrZAQ@mail.gmail.com> (raw)
In-Reply-To: <CAPig+cQ4CxRo460dcTJJtV_dPH8i5HC76_gpTv8attEZ8sdMZw@mail.gmail.com>

On Wed, Jun 22, 2016 at 3:13 AM, Eric Sunshine <sunshine@sunshineco.com> wrote:
> On Tue, Jun 21, 2016 at 5:14 PM, Charles Bailey <charles@hashpling.org> wrote:
>> From: Charles Bailey <cbailey32@bloomberg.net>
>>
>> This reverts commit 4d552005323034c1d6311796ac1074e9a4b4b57e and adds an
>> alternative fix to maintain the -L --cached behavior.
>
> It is common to provide some context along with the (shortened) commit
> ID. For instance:
>
>     This reverts 4d55200 (grep: make it clear i-t-a entries are
>     ignored, 2015-12-27) and adds ...

And that could be produced with some git alias like

git config alias.one 'show -s --date=short --pretty='format:%h (%s - %ad)'

No point in manually copy/pasting the context.
-- 
Duy

      reply	other threads:[~2016-06-22 16:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21 21:14 [PATCH v2 1/2] Fix duplicated test name Charles Bailey
2016-06-21 21:14 ` [PATCH v2 2/2] grep: fix grepping for "intent to add" files Charles Bailey
2016-06-21 22:49   ` Junio C Hamano
2016-06-22 16:11     ` Duy Nguyen
2016-06-22 18:00       ` Junio C Hamano
2016-06-22 18:32         ` Duy Nguyen
2016-06-22 19:17           ` Junio C Hamano
2016-06-22  1:13   ` Eric Sunshine
2016-06-22 16:01     ` Duy Nguyen [this message]

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='CACsJy8Biaowr-XoaJgOCXjDGre==CzeSyADftCAdzxFHoxrZAQ@mail.gmail.com' \
    --to=pclouds@gmail.com \
    --cc=charles@hashpling.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=sunshine@sunshineco.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).