- First, you need to open cmd in the admin mode, then run all commands below one by one.
- For x86 and x64
cd /d %ProgramFiles(x86)%\Microsoft Office\Office16
cd /d %ProgramFiles%\Microsoft Office\Office16
cd /d %ProgramFiles(x86)%\Microsoft Office\Office16
cd /d %ProgramFiles%\Microsoft Office\Office16
#-*- coding=utf-8 -*- | |
import requests | |
import re | |
import sys | |
reload(sys) | |
sys.setdefaultencoding('utf8') | |
signin='http://v2ex.com/signin' | |
home='http://v2ex.com' |
Use case: You have repository A with remote location rA, and repository B (which may or may not have remote location rB). You want to do one of two things:
NB: Check out git subtree
/git submodule
and this Stack Overflow question before going through the steps below. This gist is just a record of how I solved this problem on my own one day.
Before starting, make sure your local and remote repositories are up-to-date with all changes you need. The following steps use the general idea of changing the remote origin and renaming the local master branch of one of the repos in order to combine the two master branches.
#define _UNICODE | |
#define UNICODE | |
#include <windows.h> | |
#ifdef __cplusplus | |
#include <cstdio> | |
#else | |
#include <stdio.h> | |
#endif |
import Foundation | |
// A playground to see different ways to get environment variables in Swift | |
// Foundation is the easiest way using the awesome ProcessInfo class. | |
// Get all of the environment variables for your running process in a Dictionary. | |
let foundationEnv = ProcessInfo().environment | |
print("********** ProcessInfo Environment **********") |
#!/usr/bin/env bash | |
SEARCH="RemCom" | |
REPLACE=`cat /dev/urandom | tr -dc '[:alpha:]' | fold -w 8 | head -n 1` | |
git clone -q https://github.com/kavika13/RemCom RemComObf | |
find RemComObf -type f -exec sed -i -e "s/${SEARCH}/${REPLACE}/g" {} \; | |
sed -i "s/A service Cannot be started directly./Nothing's here.../g" RemComObf/RemComSvc/Service.cpp |
A list of useful Google Dorks queries and explanations. Feel free to improve with your own payloads and techniques. Go ahead an make a pull request.
Every section contains the following information: