It seems a bit unlikely bitbucket would not check authentication for secure repos on 'Incoming'! Checking further, I confirm my initial results. With a password I know to be false I get: Pull: fail Imcoming: fail test: fail With a password I know to be correct I get: Pull: fail Incoming: works Test: works This only happens with the password is URL-embedded. When it's not (and I am prompted for the password) it functions normally.
---------------------------------------- >> Yep, when I select 'pull' from the menu, and credentials are being held in >> the URL, it fails. I can however use 'Incoming' and then accept the changes. > > That's the exact opposite way I would expect things to break. The > difference is probably that incoming is not being authenticated while > pull is, and your password is simply wrong. That's the only > possibility that makes any sense. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
