From: Jeff King <peff@peff.net>
To: pedro rijo <pedrorijo91@gmail.com>
Cc: Samuel Lijin <sxlijin@gmail.com>,
e@80x24.org, Git Users <git@vger.kernel.org>
Subject: Re: git-scm.com status report
Date: Fri, 3 Feb 2017 23:24:08 +0100 [thread overview]
Message-ID: <20170203222407.ctr6bchtpblelqgb@sigill.intra.peff.net> (raw)
In-Reply-To: <CAPMsMoAUcVteJGfyYrL1ZkNLnoRES0yZxkMZeL347Q_1Kx5VBQ@mail.gmail.com>
On Fri, Feb 03, 2017 at 09:23:33PM +0000, pedro rijo wrote:
> Seems a good idea. I will start by going through some old prs/issues to
> look for trash. If I do find some like the one I referred I will let you
> know by mentioning you. After that I will have a look at simpler issues/prs.
>
> Let me know if you do agree (or you recommend another workflow) so that I
> can start looking at it this weekend :)
That sounds perfect. Thanks!
-Peff
next prev parent reply other threads:[~2017-02-03 22:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16F9F83D-5A7F-4059-9A27-DB25A8FB1E99@gmail.com>
2017-02-02 22:51 ` git-scm.com status report Samuel Lijin
2017-02-03 12:08 ` Jeff King
[not found] ` <CAPMsMoAUcVteJGfyYrL1ZkNLnoRES0yZxkMZeL347Q_1Kx5VBQ@mail.gmail.com>
2017-02-03 22:24 ` Jeff King [this message]
[not found] ` <CAPMsMoDpAeD0hpPuLeWO2T1VoEZDf_hD2gA2GDBqypMF9V6gAw@mail.gmail.com>
2017-02-20 7:53 ` Jeff King
2017-02-02 2:33 Jeff King
2017-02-02 4:36 ` Eric Wong
2017-02-02 6:54 ` Samuel Lijin
2017-02-03 11:58 ` Jeff King
2017-02-03 20:56 ` Samuel Lijin
2017-02-05 20:11 ` Pranit Bauva
2017-02-06 16:24 ` Jeff King
2017-02-06 18:27 ` Jeff King
2017-02-09 2:12 ` brian m. carlson
2017-02-09 2:50 ` Jeff King
2017-02-09 4:30 ` Eric Wong
2017-05-17 1:56 ` Samuel Lijin
2017-05-17 2:03 ` Jeff King
2017-05-18 12:06 ` Lars Schneider
2017-05-18 15:42 ` 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
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=20170203222407.ctr6bchtpblelqgb@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=pedrorijo91@gmail.com \
--cc=sxlijin@gmail.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).