From: Dave MacFarlane <driusan@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] git client-ish
Date: Mon, 5 Dec 2016 12:14:01 -0500 [thread overview]
Message-ID: <CAG2UyHpZ-X7DkbrWBpSuuha9JXgKuiPVRMD-nMwgzictqqgwrw@mail.gmail.com> (raw)
In-Reply-To: <10F39B2A-21CA-4A95-905D-9F89067A8BBD@gmail.com>
On Sat, Dec 3, 2016 at 8:12 PM, Chris McGee <newton688@gmail.com> wrote:
>
> The tests seem to be passing. I will try more rigorous tests. If the github
> bug gets fixed then I can submit pull requests.
The bug that was preventing me from pushing to GitHub is now fixed, so
if you update
feel free to pull request away.
- Dave
next prev parent reply other threads:[~2016-12-05 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 19:20 Dave MacFarlane
2016-12-03 20:05 ` Bakul Shah
2016-12-04 1:12 ` Chris McGee
2016-12-04 2:14 ` Dave MacFarlane
2016-12-05 17:14 ` Dave MacFarlane [this message]
2016-12-05 18:49 ` Chris McGee
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=CAG2UyHpZ-X7DkbrWBpSuuha9JXgKuiPVRMD-nMwgzictqqgwrw@mail.gmail.com \
--to=driusan@gmail.com \
--cc=9fans@9fans.net \
/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).