[petsc-dev] meaning of PETSC_USE_EXTERN_CXX?

[Sean Farley]

Jed Brown writes:

> On Tue, Mar 5, 2013 at 6:58 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
>
>>  I have created a fork https://bitbucket.org/BarryFSmith/petsc-dev-simp this contains all my changes plus Jed's changes with PETSC_INTERN. It
>> works on all configurations I tried.
>>
>>    I propose:
>>
>>        Jed check it out and fix any thing I broke ASAP.
>>
>
> Unfortunately, gitifyhg is slow for these one-shot pulls, mainly because hg
> bookmarks and branches are not namespaced. Perhaps we can hack a
> namespacing using the (perpetually unstable) Python API to make these
> fast.

Huh? gitifyhg should only be pulling the new changesets (isn't it
keeping some kind of hash mapping around?). Namespacing is completely
unrelated to this, and IMO, unnecessary. For something as easy as this
clean-up, all you need is one bookmark. If you want to get fancy, then
you could clean-up history and whatnot but as I mentioned before,
Bitbucket doesn't allow it. You could, of course, host your own server
(ala Rhodecode) or, you know, quit your bitching and shoehorning
unneeded concepts (namespaces, in this case).

Your comment about a perpetually unstable Python API is a strawman. You
must be using private functions and not the command server / API.