From: Siddharth Kannan <kannan.siddharth12@gmail.com>
To: mash <mash+git@crossperf.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Vegard Nossum <vegard.nossum@oracle.com>,
stepnem@gmail.com, Stefan Beller <sbeller@google.com>,
Vedant Bassi <sharababy.dev@gmail.com>,
Prathamesh Chavan <pc44800@gmail.com>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH v2 GSoC RFC] diff: allow "-" as a short-hand for "last branch"
Date: Fri, 10 Mar 2017 05:00:46 +0000 [thread overview]
Message-ID: <20170310050046.GB2417@instance-1.c.mfqp-source.internal> (raw)
In-Reply-To: <1cmCXH-0000ND-9K@crossperf.com>
On Fri, Mar 10, 2017 at 04:52:07AM +0000, mash wrote:
> Maybe you can reuse the diff tests. I'll do another microproject then.
Yeah, definitely. If there are more tests required, then I will reuse
your ones!
>
> mash
>
> The original message doesn't seem to cc the mailing list:
Thanks! It was rather daft of me to not realise this. I was waiting
for it to appear on public-inbox.
I re-sent it with the CC. The timestamp is a little bit
skewed, but I think it should make sense.
Thanks,
Siddharth.
next prev parent reply other threads:[~2017-03-10 5:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 9:50 [PATCH] diff: allow "-" as a short-hand for "last branch" mash
2017-03-09 20:26 ` [PATCH v2 GSoC RFC] " mash
[not found] ` <20170310034106.GB1984@instance-1.c.mfqp-source.internal>
2017-03-10 4:52 ` mash
2017-03-10 5:00 ` Siddharth Kannan [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-10 4:59 Siddharth Kannan
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170310050046.GB2417@instance-1.c.mfqp-source.internal \
--to=kannan.siddharth12@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mash+git@crossperf.com \
--cc=pc44800@gmail.com \
--cc=sbeller@google.com \
--cc=sharababy.dev@gmail.com \
--cc=stepnem@gmail.com \
--cc=vegard.nossum@oracle.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).