From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] document.removeAttribute
Date: Thu, 19 Jan 2017 12:32:04 -0800 [thread overview]
Message-ID: <87k29qx03f.fsf@the-brannons.com> (raw)
In-Reply-To: <20170119200417.GA5912@odin> (Adam Thompson's message of "Thu, 19 Jan 2017 20:04:18 +0000")
Adam Thompson <arthompson1990@gmail.com> writes:
> Alternatively I can push to my fork of the edbrowse repo and raise a pull
> request (though I'm not sure how to raise one with edbrowse).
There's a great tool for sending pull requests from the command line.
It's called hub, and I think it's packaged by most distros.
I use this all the time, and it's a breeze.
Just git push to a branch and hub pull-request (with the correct args).
Pull requests are ok, but a patch is probably better, since everyone
will see it.
Also one thing I'm thinking about doing is tightening up our github
integration. I think I could get github to send mail to this list every
time a pull request or issue is opened, or whenever someone pushes to
the repo. Would that be appreciated, or would it be too spammy for
everyone?
I already get mail on new issues / pull requests, and I believe that Karl does
as well.
-- Chris
next prev parent reply other threads:[~2017-01-19 20:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 20:04 Adam Thompson
2017-01-19 20:32 ` Chris Brannon [this message]
2017-01-19 21:34 ` Kevin Carhart
2017-01-24 8:43 ` Adam Thompson
2017-01-24 19:08 ` Adam Thompson
2017-01-24 20:48 ` Karl Dahlke
2017-01-24 22:08 ` Kevin Carhart
[not found] ` <20170024174651.eklhad@comcast.net>
2017-01-24 23:57 ` Kevin Carhart
2017-01-25 1:50 ` Karl Dahlke
2017-01-21 0:27 ` Karl Dahlke
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=87k29qx03f.fsf@the-brannons.com \
--to=chris@the-brannons.com \
--cc=Edbrowse-dev@lists.the-brannons.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).