why: see https://stackoverflow.com/a/20653073/2249526
https://stackoverflow.com/a/29888735/2249526
If you already have checked out the code, the files are already indexed. After changing your git settings, say by running:
why: see https://stackoverflow.com/a/20653073/2249526
https://stackoverflow.com/a/29888735/2249526
If you already have checked out the code, the files are already indexed. After changing your git settings, say by running:
Git for Windows comes bundled with the "Git Bash" terminal which is incredibly handy for unix-like commands on a windows machine. It is missing a few standard linux utilities, but it is easy to add ones that have a windows binary available.
The basic idea is that C:\Program Files\Git\mingw64\
is your /
directory according to Git Bash (note: depending on how you installed it, the directory might be different. from the start menu, right click on the Git Bash icon and open file location. It might be something like C:\Users\name\AppData\Local\Programs\Git
, the mingw64
in this directory is your root. Find it by using pwd -W
).
If you go to that directory, you will find the typical linux root folder structure (bin
, etc
, lib
and so on).
If you are missing a utility, such as wget, track down a binary for windows and copy the files to the corresponding directories. Sometimes the windows binary have funny prefixes, so
#!/usr/bin/env bash | |
# | |
#### Source: http://www.taddong.com/tools/TLSSLed_v1.3.sh | |
# | |
# | |
# Tool: | |
# TLSSLed.sh | |
# | |
# Description: | |
# Script to extract the most relevant security details from a |
import jenkins.model.* | |
def matchedJobs = Jenkins.instance.items.findAll { job -> | |
job.name =~ /^OpenShift sample$/ | |
} | |
matchedJobs.each { job -> | |
println "jobs: ${job.name}" | |
//job.delete() | |
} |
## Tested with tmux 1.8 | |
# C-b is not acceptable -- Vim uses it | |
set-option -g prefix C-a | |
bind-key C-a last-window | |
# Start numbering at 1 | |
set -g base-index 1 |
SHOW DATABASES
USE "db"
> SHOW MEASUREMENTS # similar to tables in RDBs
name: measurements
name
----
oc get pod -o jsonpath='{range .items[*]}{"SPEC: \n LIMITS : "}{.spec.containers[*].resources.limits}{"\n REQUESTS: "}{.spec.containers[*].resources.requests}{"\n"}{end}'
oc get pod -o jsonpath='{range .items[*]}{"NAME: "}{.metadata.name}{"\nSPEC: \n LIMITS : "}{.spec.containers[*].resources.limits}{"\n REQUESTS: "}{.spec.containers[*].resources.requests}{"\n\n"}{end}'
Use merge --squash to squash multiple commits into a single commit (without a merge commit!).
Omitting -m
at the final commit command will display all commit messages of bugfix branch and lets you edit the new commit message.
Switch to the master branch and make sure you are up to date:
git checkout master && git pull
pucl listAvailablePackages -repositories E:\Daten\WAS9\Fixpacks\SDK_8.0.6.6\ibm-java-sdk-8.0-6.6-linux-x64-installmgr.zip
com.ibm.java.jdk.v8_8.0.6006.20200220_0710
pucl listAvailablePackages -repositories E:\Daten\WAS9\Fixpacks\SDK_8.0.5.41\ibm-java-sdk-8.0-5.41-linux-x64-installmgr.zip
com.ibm.java.jdk.v8_8.0.5041.20190924_1031
git clone --no-checkout git@github.com:thikade/docker-jig.git
cd docker-jig
git config core.sparseCheckout true
echo "grafana/dashboards/*" > .git/info/sparse-checkout
git checkout thikade