Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

[Qt] Fix display of package name on 'open config file' tooltip #11198

Merged
merged 1 commit into from Sep 2, 2017

Conversation

Projects
None yet
5 participants
Contributor

esotericnonsense commented Aug 30, 2017

This patch addresses #11197.

Member

MarcoFalke commented Aug 30, 2017

utACK 6c26e89

Member

achow101 commented Aug 30, 2017

utACK 6c26e89

@MarcoFalke MarcoFalke added this to the 0.15.0 milestone Aug 30, 2017

Member

MarcoFalke commented Aug 30, 2017

Marked for backport in case it can make it through. Imo, does not need a fresh rc.

Contributor

esotericnonsense commented Aug 30, 2017

I have tested this patch off the v0.15.0rc3 tag with --disablewallet (as I don't have bdb4.8 on the machine atm).

Contributor

esotericnonsense commented Aug 30, 2017

Also working on a PR against master as it doesn't merge cleanly

@esotericnonsense esotericnonsense changed the base branch from 0.15 to master Aug 30, 2017

Contributor

paveljanik commented Sep 1, 2017

ACK 14ccd4d

@MarcoFalke MarcoFalke merged commit 14ccd4d into bitcoin:master Sep 2, 2017

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

MarcoFalke added a commit that referenced this pull request Sep 2, 2017

Merge #11198: [Qt] Fix display of package name on 'open config file' …
…tooltip


14ccd4d [Qt] Fix display of package name on 'open config file' tooltip (Daniel Edgecumbe)

Pull request description:

  This patch addresses #11197.

Tree-SHA512: b826fa2eb69f2c8054d2e84614e067bb00d2176701992dadfea01c2ad63d29015acdb76c5b874f5f6bda52b1f05e3ccfa1b67a4ee2f1e0c26496d1ff1718f325
Member

jonasschnelli commented Sep 3, 2017

Post merge ACK 14ccd4d

@MarcoFalke MarcoFalke modified the milestones: 0.15.1, 0.15.0 Sep 5, 2017

MarcoFalke added a commit to MarcoFalke/bitcoin that referenced this pull request Oct 3, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment