From: "Jordan McCullough (GitHub Staff)" <training@github.com>
To: Felipe Contreras <felipe.contreras@gmail.com>,
Chris Packham <judge.packham@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Re: material for git training sessions/presentations
Date: Tue, 06 May 2014 15:20:18 -0700 [thread overview]
Message-ID: <discussions/cb0b63ead41211e398260b8f9a8fb553/comments/1044478@github.com> (raw)
In-Reply-To: <53671965621e_25b273930894@nysa.notmuch>
Hi Felipe,
Jordan McCullough here from the GitHub Training team. I noticed you were kind enough to open a Pull Request (linked below for reference) addressing this. We really do appreciate the contribution.
I'll review the PR just as soon as I can, so anticipate a merge with your changes to the `color.ui` soon.
https://github.com/github/training-kit/pull/118
Commit and Octocats,
Jordan
next prev parent reply other threads:[~2014-05-06 22:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 4:18 material for git training sessions/presentations Chris Packham
2014-05-05 4:29 ` Scott Chacon
2014-05-05 4:53 ` Felipe Contreras
2014-05-06 5:01 ` Jason St. John
2014-05-06 22:20 ` Jordan McCullough (GitHub Staff) [this message]
2014-05-07 15:02 ` Sitaram Chamarty
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=discussions/cb0b63ead41211e398260b8f9a8fb553/comments/1044478@github.com \
--to=training@github.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=judge.packham@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.
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).