Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Delivered-To: kanepyork+coding@gmail.com
- Received: by 10.60.31.48 with SMTP id x16csp45212oeh;
- Tue, 19 Mar 2013 18:28:30 -0700 (PDT)
- X-Received: from mr.google.com ([10.180.74.131])
- by 10.180.74.131 with SMTP id t3mr640490wiv.23.1363742910323 (num_hops = 1);
- Tue, 19 Mar 2013 18:28:30 -0700 (PDT)
- X-Received: by 10.180.74.131 with SMTP id t3mr526208wiv.23.1363742909953;
- Tue, 19 Mar 2013 18:28:29 -0700 (PDT)
- X-Forwarded-To: kanepyork+coding@gmail.com
- X-Forwarded-For: rikingcoding@gmail.com kanepyork+coding@gmail.com
- Delivered-To: rikingcoding@gmail.com
- Received: by 10.194.176.163 with SMTP id cj3csp46871wjc;
- Tue, 19 Mar 2013 18:28:29 -0700 (PDT)
- X-Received: by 10.60.29.129 with SMTP id k1mr3058822oeh.8.1363742908418;
- Tue, 19 Mar 2013 18:28:28 -0700 (PDT)
- Return-Path: <bounce+dca5e3.b3e-rikingcoding=gmail.com@github.com>
- Received: from rs224.mailgun.us (rs224.mailgun.us. [209.61.151.224])
- by mx.google.com with ESMTP id z10si7140oew.1.2013.03.19.18.28.27;
- Tue, 19 Mar 2013 18:28:28 -0700 (PDT)
- Received-SPF: pass (google.com: domain of bounce+dca5e3.b3e-rikingcoding=gmail.com@github.com designates 209.61.151.224 as permitted sender) client-ip=209.61.151.224;
- Authentication-Results: mx.google.com;
- spf=pass (google.com: domain of bounce+dca5e3.b3e-rikingcoding=gmail.com@github.com designates 209.61.151.224 as permitted sender) smtp.mail=bounce+dca5e3.b3e-rikingcoding=gmail.com@github.com;
- dkim=pass header.i=@github.com
- DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=github.com; q=dns/txt;
- s=mailo; t=1363742907; h=Date: From: To: Message-Id: In-Reply-To:
- References: Subject: Mime-Version: Content-Type:
- Content-Transfer-Encoding: Sender;
- bh=HdPpGvJL0vcg1bjmuAAsNGgaKS/8G0XLUrTMaPD38kc=; b=Gyuq3Q1dV0Nv6s49EvM5rwk5PDhOJHcTbOb5CdgX4i1S5MUcaW5JPvnX8QK+ECflJ6aXWilc
- oJpgDH2+t3CPD/C85NQjITQWDzZCcXDSgcemNg2WwBOdn0uIr927offVxoVhdn6mbL8b4Whp
- m8gcKqeKymHrG3iONNepR9aPIew=
- DomainKey-Signature: a=rsa-sha1; c=nofws; d=github.com; s=mailo; q=dns;
- h=Date: From: To: Message-Id: In-Reply-To: References: Subject:
- Mime-Version: Content-Type: Content-Transfer-Encoding: Sender;
- b=PVuB+cSAfTPLc5EpgeLKD6yK+fwshoZJAI67WR0xXF1n3aaAEQiYzd9kdEc5YJDivV2WEa
- X7a9A6f0iKDZRgzQumTKY0DCcLj678B9UxOObFfqLPYhcqBxMJW79RZ85LJqNGnZVUr+Q3rp
- yFYj1vGV8h3xXwtIRJMPBe5/giSFY=
- Received: by luna.mailgun.net with SMTP mgrt 8759342799429; Wed, 20 Mar 2013
- 01:28:27 +0000
- Received: from github.com (ec2-50-17-66-69.compute-1.amazonaws.com
- [50.17.66.69]) by mxa.mailgun.org with ESMTP id 514910ba.7f78e80ff630-in1;
- Wed, 20 Mar 2013 01:28:26 -0000 (UTC)
- Date: Tue, 19 Mar 2013 18:28:26 -0700
- From: Matthew McCullough <support@github.com> (GitHub Staff)
- To: rikingcoding@gmail.com
- Message-Id: <discussions/8ec62d46903b11e29f996ec54f2f9481/comments/9@github.com>
- In-Reply-To: <discussions/8ec62d46903b11e29f996ec54f2f9481/comments/8@github.com>
- References: <5147cb648b3ac_79b99c9e10834c0@fe13.rs.github.com.mail>
- <discussions/8ec62d46903b11e29f996ec54f2f9481/comments/2@github.com>
- <discussions/8ec62d46903b11e29f996ec54f2f9481/comments/3@github.com>
- <discussions/8ec62d46903b11e29f996ec54f2f9481/comments/4@github.com>
- <discussions/8ec62d46903b11e29f996ec54f2f9481/comments/5@github.com>
- <discussions/8ec62d46903b11e29f996ec54f2f9481/comments/6@github.com>
- <discussions/8ec62d46903b11e29f996ec54f2f9481/comments/7@github.com>
- <discussions/8ec62d46903b11e29f996ec54f2f9481/comments/8@github.com>
- Subject: Re: Deleted user's PR
- Mime-Version: 1.0
- Content-Type: text/plain; charset="UTF-8"
- Content-Transfer-Encoding: 7bit
- X-Mailgun-Sid: WyI0YjA3MiIsICJyaWtpbmdjb2RpbmdAZ21haWwuY29tIiwgImIzZSJd
- Sender: support=github.com@github.com
- Kane,
- A quick update. We're still working this on our side, looking at the integrity of the repo. However, we have solved the Pull Request issue. That PR has been deleted, as it didn't have any refs/commits attached to it on our side.
- Cheers,
- -Matthew
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement