public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Useful bitcoin patches...
Date: Thu, 4 Aug 2011 16:29:01 -0400	[thread overview]
Message-ID: <201108041629.04130.luke@dashjr.org> (raw)
In-Reply-To: <201107101442.43605.luke@dashjr.org>

Reminder these are still ready for merging...

Jeff, you seem to have rewritten *part of* bugfix_CreateThread_leak and 
neglected to attribute the original author (as my branch did/does).

> For the "3diff" version, I extracted and made proper git branches for each
> logical part:
>   hub_mode
>   threaded_rpc
>   \-- rpc_keepalive (depends on threaded_rpc, or a single connection would
>                      keep the JSON-RPC interface locked up)
>   signal_blk_notify (generic version of -pollpidfile, with a bugfix)
>   bugfix_CreateThread_leak
>   getwork_dedupe (original branch for my bugfix)
> 
> In addition, I also consider these branches valid candidates for merging:
>   coinbaser (popens a given command and reads coinbase outputs from stdout)
>   gitignore (ignore some common misc files)
>   minfee_modes (internal function changes to allow specifying different
> fees for relay, send, or accept-in-block)
>   \-- eligius_relay (relay lower fees only Eligius will accept)
>       \-- eligius_sendfee (send lower fees only Eligius will accept)
>   txinfo (adds entries to getinfo for transactions accepted for relaying,
>           transactions accepted for the current block-in-progress, and
> current block-in-progress size)
>   bitcoinuri (compliant support for all bitcoin: URIs)
> 
> All available from git://gitorious.org/~Luke-Jr/bitcoin/luke-jr-bitcoin.git



  parent reply	other threads:[~2011-08-04 20:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01  3:23 [Bitcoin-development] Useful bitcoin patches Jeff Garzik
2011-07-01 16:03 ` Christian Decker
2011-07-01 16:23   ` Gregory Maxwell
2011-07-01 16:25   ` Matt Corallo
2011-07-01 18:59 ` Luke-Jr
2011-07-10 18:42 ` Luke-Jr
2011-07-10 19:12   ` Matt Corallo
2011-07-10 20:30     ` Luke-Jr
     [not found]       ` <1310335963.2230.29.camel@Desktop666>
     [not found]         ` <201107101846.09997.luke@dashjr.org>
2011-07-10 22:58           ` Matt Corallo
2011-08-04 20:29   ` Luke-Jr [this message]
2011-08-04 20:42     ` Luke-Jr
2011-08-04 23:43     ` Jeff Garzik
2011-08-05  3:01       ` Luke-Jr
2011-09-03 15:27     ` [Bitcoin-development] Last try: Fixes for 0.4 Luke-Jr

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=201108041629.04130.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-development@lists.sourceforge.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