From: jas@corpus-callosum.com (Jeff Sickel)
Subject: [9fans] How and where to submit a patch for acme?
Date: Wed, 30 Mar 2011 00:05:54 -0500 [thread overview]
Message-ID: <F0F1E068-E9C8-4946-999E-237FF391ECE7@corpus-callosum.com> (raw)
In-Reply-To: <AANLkTi=fA497XTFbs05Q3qcawAt_pO-Uriehczxso60C@mail.gmail.com>
On Mar 29, 2011, at 2:45 PM, John Floren wrote:
> On Tue, Mar 29, 2011 at 12:17 PM, erik quanstrom
> <quanstro at labs.coraid.com> wrote:
>>>
>> except to talk to russ.
>>
>
> In this case, if you have a bitbucket account, just make a fork of
> russ's repo, make the change in your fork, then send Russ a pull
> request on bitbucket.
and:
9 man codereview
next prev parent reply other threads:[~2011-03-30 5:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.9.1301422307.18267.9fans@9fans.net>
[not found] ` <20110329190348.GF29452@jagpc2.oldgcts>
2011-03-29 19:05 ` John A. Grahor
2011-03-29 19:17 ` erik quanstrom
2011-03-29 19:45 ` John Floren
2011-03-30 5:05 ` Jeff Sickel [this message]
2011-03-29 17:46 John A. Grahor
2011-03-29 17:58 ` John Floren
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=F0F1E068-E9C8-4946-999E-237FF391ECE7@corpus-callosum.com \
--to=jas@corpus-callosum.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).