From: Stefan Beller <sbeller@google.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Jeff Hostetler <jeffhost@microsoft.com>,
Junio C Hamano <gitster@pobox.com>,
GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH] list-objects-filter-options: fix up some sparse warnings
Date: Tue, 21 Nov 2017 16:23:30 -0800 [thread overview]
Message-ID: <CAGZ79kaKWRMDFQLbeRtGmejOD7JD_RCjK5J_HOFqddReT6yOEA@mail.gmail.com> (raw)
In-Reply-To: <b5a6ddb1-0971-92d1-4cfb-94366d8f14c3@ramsayjones.plus.com>
> [It would probably be easier if I used git to output this for me, rather
> than typing it into my email client!]
git config alias.gcs "show --date=short -s --pretty='format:%h ("%s", %ad)'"
will make you the `git gcs` alias that I use to describe commits.
next prev parent reply other threads:[~2017-11-22 0:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 23:39 [PATCH] list-objects-filter-options: fix up some sparse warnings Ramsay Jones
2017-11-21 1:16 ` Jonathan Nieder
2017-11-21 11:04 ` Ramsay Jones
2017-11-22 0:23 ` Stefan Beller [this message]
2017-11-21 12:36 ` Jeff Hostetler
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=CAGZ79kaKWRMDFQLbeRtGmejOD7JD_RCjK5J_HOFqddReT6yOEA@mail.gmail.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jeffhost@microsoft.com \
--cc=jrnieder@gmail.com \
--cc=ramsay@ramsayjones.plus.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).