Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

75,411

Downloads of v 2024.2.0:

825

Last Update:

06 Jun 2024

Package Maintainer(s):

Software Author(s):

  • Perforce Software
  • Inc.

Tags:

freeware p4merge diff merge admin

P4Merge, the Perforce Visual Merge Tool

  • 1
  • 2
  • 3

2024.2.0 | Updated: 06 Jun 2024

Downloads:

75,411

Downloads of v 2024.2.0:

825

Maintainer(s):

Software Author(s):

  • Perforce Software
  • Inc.

P4Merge, the Perforce Visual Merge Tool 2024.2.0

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install P4Merge, the Perforce Visual Merge Tool, run the following command from the command line or from PowerShell:

>

To upgrade P4Merge, the Perforce Visual Merge Tool, run the following command from the command line or from PowerShell:

>

To uninstall P4Merge, the Perforce Visual Merge Tool, run the following command from the command line or from PowerShell:

>

Deployment Method:

NOTE

This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade p4merge -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade p4merge -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Install p4merge
  win_chocolatey:
    name: p4merge
    version: '2024.2.0'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'p4merge' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2024.2.0'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller p4merge
{
    Name     = "p4merge"
    Version  = "2024.2.0"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'p4merge':
  ensure   => '2024.2.0',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved as a trusted package on 22 Jul 2024.

Description

P4Merge

P4Merge is a visual diff tool that displays the differences between file versions and helps you
to resolve conflicts and merge competing versions into one.

Package-specific issue

If this package isn't up-to-date for some days, Create an issue

Support the package maintainer and Patreon


tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';

$packageName      = $env:ChocolateyPackageName
$toolsDir         = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$file             = Join-Path $toolsDir '/p4vinst64.exe'
$checksum         = 'F12BB464DC33A75557F5FF4211AD9619A61D89D912C819C9F2F1D4D37CCB4848'
$checksumType     = 'sha256'

$packageArgs = @{
  packageName     = $packageName
  unzipLocation   = $toolsDir
  fileType        = 'EXE'
  file            = $file

  softwareName    = 'Helix Core*'

  validExitCodes= @(0, 3010, 1641)
  silentArgs   = '/s REMOVEAPPS=P4V,P4ADMIN,P4'
}

Install-ChocolateyInstallPackage @packageArgs
tools\LICENSE.txt
Helix Admin, the Helix Administration Tool
Helix P4Merge, the Helix  Visual Merge Tool
Helix Visual Client (P4V)
Copyright (c) 2018, Perforce Software, Inc.  All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1.  Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2.  Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL PERFORCE SOFTWARE, INC. BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

----------------------------------------

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/) This product includes software and cryptographic software written by Eric Young ([email protected]). This product includes software written by Tim Hudson ([email protected]). http://www.openssl.org/source/license.html 

  LICENSE ISSUES
  ==============

  The OpenSSL toolkit stays under a double license, i.e. both the conditions of
  the OpenSSL License and the original SSLeay license apply to the toolkit.
  See below for the actual license texts.

        OpenSSL License
        ---------------

        Copyright (c) 1998-2011 The OpenSSL Project.  All rights reserved.
        
        Redistribution and use in source and binary forms, with or without
        modification, are permitted provided that the following conditions
        are met:
        
        1. Redistributions of source code must retain the above copyright
           notice, this list of conditions and the following disclaimer.
        
        2. Redistributions in binary form must reproduce the above copyright
           notice, this list of conditions and the following disclaimer in
           the documentation and/or other materials provided with the
           distribution.
        
        3. All advertising materials mentioning features or use of this
           software must display the following acknowledgment:
           "This product includes software developed by the OpenSSL Project
           for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
        
        4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
           endorse or promote products derived from this software without
           prior written permission. For written permission, please contact
           [email protected].
        
        5. Products derived from this software may not be called "OpenSSL"
           nor may "OpenSSL" appear in their names without prior written
           permission of the OpenSSL Project.
        
        6. Redistributions of any form whatsoever must retain the following
           acknowledgment:
           "This product includes software developed by the OpenSSL Project
           for use in the OpenSSL Toolkit (http://www.openssl.org/)"
        
        THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
        EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
        IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
        PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE OpenSSL PROJECT OR
        ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
        SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
        NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
        LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
        HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
        STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
        ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
        OF THE POSSIBILITY OF SUCH DAMAGE.
        
        This product includes cryptographic software written by Eric Young
        ([email protected]).  This product includes software written by Tim
        Hudson ([email protected]).
        
        Original SSLeay License
        -----------------------

        Copyright (C) 1995-1998 Eric Young ([email protected])
        All rights reserved.
        
        This package is an SSL implementation written
        by Eric Young ([email protected]).
        The implementation was written so as to conform with Netscapes SSL.
        
        This library is free for commercial and non-commercial use as long as
        the following conditions are adhered to.  The following conditions
        apply to all code found in this distribution, be it the RC4, RSA,
        lhash, DES, etc., code; not just the SSL code.  The SSL documentation
        included with this distribution is covered by the same copyright terms
        except that the holder is Tim Hudson ([email protected]).
        
        Copyright remains Eric Young's, and as such any Copyright notices in
        the code are not to be removed.
        If this package is used in a product, Eric Young should be given attribution
        as the author of the parts of the library used.
        This can be in the form of a textual message at program startup or
        in documentation (online or textual) provided with the package.
        
        Redistribution and use in source and binary forms, with or without
        modification, are permitted provided that the following conditions
        are met:
        1. Redistributions of source code must retain the copyright
           notice, this list of conditions and the following disclaimer.
        2. Redistributions in binary form must reproduce the above copyright
           notice, this list of conditions and the following disclaimer in the
           documentation and/or other materials provided with the distribution.
        3. All advertising materials mentioning features or use of this software
           must display the following acknowledgement:
           "This product includes cryptographic software written by
           Eric Young ([email protected])"
           The word 'cryptographic' can be left out if the routines from the library
           being used are not cryptographic related  :-) .
        4. If you include any Windows specific code (or a derivative thereof) from
           the apps directory (application code) you must include an acknowledgement:
           "This product includes software written by Tim Hudson ([email protected])"
        
        THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
        ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
        IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
        ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
        FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
        DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
        OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
        HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
        LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
        OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
        SUCH DAMAGE.
        
        The license and distribution terms for any publicly available version or
        derivative of this code cannot be changed.  i.e. this code cannot simply be
        copied and put under another distribution license
        [including the GNU Public License.]


----------------------------------------
Qt Licensing

		This product includes QtWebKit version 5.9.1 which is licensed under the
		GNU LGPL v2.1. See https://qt.io/licensing for an overview of Qt licensing.
		Source code for QtWebKit is available from 
		ftp://ftp.perforce.com/r18.3/bin.noarch/...
		or from the source repository at https://code.qt.io/qt/qtwebkit.git

tools\p4vinst64.exe
md5: 2C4CAB3CF24B8704FE06BE2EA45363AD | sha1: DC04907FE858978C4FD78C7D9AFC66A4CB8029CA | sha256: F12BB464DC33A75557F5FF4211AD9619A61D89D912C819C9F2F1D4D37CCB4848 | sha512: EA71B6878C74558BB4D98E34635800EB4C4F8F97197587A91C2538FCB02205CF00E58CE06CE250FFA805705149CBBFF49A3354DEC5FF6CC945E06CFA4D898958
tools\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The installer have been downloaded from the official mirror and can be verified like this:

1. Download the following installer(s):

link: https://cdist2.perforce.com/perforce/r24.2/bin.ntx64/p4vinst64.exe

2. You can use one of the following methods to obtain the checksum(s):
  - Use powershell function 'Get-Filehash'
  - Use chocolatey utility 'checksum.exe'

checksumtype: sha256
checksum: F12BB464DC33A75557F5FF4211AD9619A61D89D912C819C9F2F1D4D37CCB4848

The included 'LICENSE.txt' file have been obtained from:
license: https://cdist2.perforce.com/perforce/r14.1/doc/user/p4v_license.txt

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
P4Merge, the Perforce Visual Merge Tool 2024.1.0 1045 Wednesday, March 20, 2024 Approved
P4Merge, the Perforce Visual Merge Tool 2023.4.0 1192 Thursday, December 21, 2023 Approved
P4Merge, the Perforce Visual Merge Tool 2023.3.0 976 Tuesday, October 3, 2023 Approved
P4Merge, the Perforce Visual Merge Tool 2023.2 1758 Friday, May 19, 2023 Approved
P4Merge, the Perforce Visual Merge Tool 2023.1 1153 Tuesday, February 28, 2023 Approved
P4Merge, the Perforce Visual Merge Tool 2022.3.0.2022112301 1483 Sunday, November 27, 2022 Approved
P4Merge, the Perforce Visual Merge Tool 2022.3 862 Thursday, November 17, 2022 Approved
P4Merge, the Perforce Visual Merge Tool 2022.2 1890 Friday, July 1, 2022 Approved
P4Merge, the Perforce Visual Merge Tool 2022.1.1 950 Wednesday, May 18, 2022 Approved
P4Merge, the Perforce Visual Merge Tool 2022.1 1008 Wednesday, March 30, 2022 Approved
P4Merge, the Perforce Visual Merge Tool 2021.4.2 329 Friday, March 25, 2022 Approved
P4Merge, the Perforce Visual Merge Tool 2021.4.1 749 Saturday, February 26, 2022 Approved
P4Merge, the Perforce Visual Merge Tool 2021.1.2 3562 Wednesday, May 12, 2021 Approved
P4Merge, the Perforce Visual Merge Tool 2021.1.1 1309 Saturday, February 20, 2021 Approved
P4Merge, the Perforce Visual Merge Tool 2021.1 541 Friday, February 5, 2021 Approved
P4Merge, the Perforce Visual Merge Tool 2020.3.1.20210203 242 Wednesday, February 3, 2021 Approved
P4Merge, the Perforce Visual Merge Tool 2020.3.1.20210202 194 Tuesday, February 2, 2021 Approved
P4Merge, the Perforce Visual Merge Tool 2020.3.1.20210201 211 Monday, February 1, 2021 Approved
P4Merge, the Perforce Visual Merge Tool 2020.3.1.20210131 165 Sunday, January 31, 2021 Approved
P4Merge, the Perforce Visual Merge Tool 2020.3.1.20210130 131 Saturday, January 30, 2021 Approved
P4Merge, the Perforce Visual Merge Tool 2020.3.1.20210129 170 Friday, January 29, 2021 Approved
P4Merge, the Perforce Visual Merge Tool 2020.3.1.20210128 173 Thursday, January 28, 2021 Approved
P4Merge, the Perforce Visual Merge Tool 2020.3.1.20210127 209 Wednesday, January 27, 2021 Approved
P4Merge, the Perforce Visual Merge Tool 2020.3.1.20210126 191 Tuesday, January 26, 2021 Approved
P4Merge, the Perforce Visual Merge Tool 2020.3.1.20210125 194 Monday, January 25, 2021 Approved
P4Merge, the Perforce Visual Merge Tool 2020.3.1.20210124 142 Sunday, January 24, 2021 Approved
P4Merge, the Perforce Visual Merge Tool 2020.3.1.20210123 128 Saturday, January 23, 2021 Approved
P4Merge, the Perforce Visual Merge Tool 2020.3.1.20210122 163 Friday, January 22, 2021 Approved
P4Merge, the Perforce Visual Merge Tool 2020.3.1.20210121 168 Thursday, January 21, 2021 Approved
P4Merge, the Perforce Visual Merge Tool 2020.3.1.20210120 215 Wednesday, January 20, 2021 Approved
P4Merge, the Perforce Visual Merge Tool 2020.3.1.20210119 166 Tuesday, January 19, 2021 Approved
P4Merge, the Perforce Visual Merge Tool 2020.3.1.20201225 1024 Friday, December 25, 2020 Approved
P4Merge, the Perforce Visual Merge Tool 2020.3.1 177 Thursday, December 24, 2020 Approved
P4Merge, the Perforce Visual Merge Tool 2020.3 544 Monday, December 7, 2020 Approved
P4Merge, the Perforce Visual Merge Tool 2020.2.20201107 719 Thursday, November 12, 2020 Approved
P4Merge, the Perforce Visual Merge Tool 2020.2.20200917 2008 Sunday, September 20, 2020 Approved
P4Merge, the Perforce Visual Merge Tool 2020.2.1 1094 Saturday, September 19, 2020 Approved
P4Merge, the Perforce Visual Merge Tool 2020.2 201 Saturday, August 22, 2020 Approved
P4Merge, the Perforce Visual Merge Tool 2019.2.1904275 8153 Tuesday, January 14, 2020 Approved
P4Merge, the Perforce Visual Merge Tool 2019.2.1883366 2450 Thursday, December 12, 2019 Approved
P4Merge, the Perforce Visual Merge Tool 2019.2.1856742 2770 Friday, October 18, 2019 Approved
P4Merge, the Perforce Visual Merge Tool 2019.1.1830398 4337 Thursday, August 22, 2019 Approved
P4Merge, the Perforce Visual Merge Tool 2018.3.1719708 7470 Monday, December 10, 2018 Approved
P4Merge, the Perforce Visual Merge Tool 2018.1.1637591 4074 Wednesday, April 4, 2018 Approved
P4Merge, the Perforce Visual Merge Tool 2017.2.1573260 2070 Wednesday, October 4, 2017 Approved
P4Merge, the Perforce Visual Merge Tool 2017.2.1535556 1080 Monday, July 31, 2017 Approved
P4Merge, the Perforce Visual Merge Tool 2017.2.1532340 749 Wednesday, July 19, 2017 Approved
P4Merge, the Perforce Visual Merge Tool 2017.2.1518788 917 Friday, June 16, 2017 Approved
P4Merge, the Perforce Visual Merge Tool 2017.1.1491634 1205 Friday, April 7, 2017 Approved
P4Merge, the Perforce Visual Merge Tool 2015.2.1 2001 Thursday, November 3, 2016 Approved
P4Merge, the Perforce Visual Merge Tool 2014.1 4682 Monday, June 2, 2014 Approved
P4Merge, the Perforce Visual Merge Tool 2013.2 1593 Saturday, June 29, 2013 Approved
P4Merge, the Perforce Visual Merge Tool 2012.2 1004 Sunday, November 25, 2012 Approved
P4Merge, the Perforce Visual Merge Tool 2011.1.1 766 Sunday, January 22, 2012 Approved
P4Merge, the Perforce Visual Merge Tool 2011.1 539 Thursday, January 12, 2012 Approved

Software

https://www.perforce.com/perforce/doc.current/user/p4vmergenotes.txt

Package


Discussion for the P4Merge, the Perforce Visual Merge Tool Package

Ground Rules:

  • This discussion is only about P4Merge, the Perforce Visual Merge Tool and the P4Merge, the Perforce Visual Merge Tool package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or P4Merge, the Perforce Visual Merge Tool, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus