[Bitcoin-development] 0.6.x - detachdb in wrong place

2012-06-17 Thread grarpamp
Well, detachdb doesn't appear in the -\? help because it's stuffed under pnp, which is not set in my build. please fix for people, tx :) #ifdef USE_UPNP #if USE_UPNP -upnp\t + _(Use Universal Plug and Play to map the listening port (default: 1)) + \n + #else

Re: [Bitcoin-development] 0.6.x - detachdb in wrong place

2012-06-17 Thread Gregory Maxwell
On Sun, Jun 17, 2012 at 5:22 AM, grarpamp grarp...@gmail.com wrote: Well, detachdb doesn't appear in the -\? help because it's stuffed under pnp, which is not set in my build. please fix for people, tx :) It isn't inside the ifdef in bitcoin git master. (For future reference this sort of

Re: [Bitcoin-development] 0.6.x - detachdb in wrong place

2012-06-17 Thread grarpamp
It isn't inside the ifdef in bitcoin git master. Oh, hmm, well then, what is the difference or usage between these two repositories in regards to the project? Which one are the formal releases tagged (tbz's cut) in? Which one has the branches with the commits that will make it into the next

Re: [Bitcoin-development] 0.6.x - detachdb in wrong place

2012-06-17 Thread Gregory Maxwell
On Sun, Jun 17, 2012 at 5:35 PM, grarpamp grarp...@gmail.com wrote: It isn't inside the ifdef in bitcoin git master. Oh, hmm, well then, what is the difference or usage between these two repositories in regards to the project? Which one are the formal releases tagged (tbz's cut) in? Which

Re: [Bitcoin-development] 0.6.x - detachdb in wrong place

2012-06-17 Thread Luke-Jr
On Sunday, June 17, 2012 11:04:42 PM grarpamp wrote: https://github.com/bitcoin/bitcoin https://git.gitorious.org/bitcoin/bitcoind-stable The latter is Luke's backports of security and stability fixes to otherwise unmaintained old versions. Ah ok, coming from cvs/svn, it's a bit

Re: [Bitcoin-development] 0.6.x - detachdb in wrong place

2012-06-17 Thread Gregory Maxwell
On Sun, Jun 17, 2012 at 7:04 PM, grarpamp grarp...@gmail.com wrote: Presumably the github/0.6.2 branch is safe for production? 0.6.2 is very widely used, more so than the other acceptably updated backports. What degree of caution about wallet eating should be made for those using