ocschwar

Cringes."

• Model: Fusion*

• Size: 768 X 768 (0.59 MP)

• Used settings:

  • Prompt: Cringes
  • Using base image: No
  • Aspect Ratio: square

Dragon and Unicorn fighting over Somerville

• Model: Fusion*

• Size: 1682 X 1249 (2.10 MP)

• Used settings:

  • Prompt: Dragon and unicorn enjoying a cloudy sunset on a street
  • Using base image: Yes

By any other name

• Model: Cyberspace (v2)*

• Size: 1682 X 1249 (2.10 MP)

• Used settings:

  • Prompt: One rose pocking through a wooden mesh
  • Using base image: Yes

What AI thinks when it's told "Massachusetts"

• Model: Quantum (v2)*

• Size: 1682 X 1249 (2.10 MP)

• Used settings:

  • Prompt: Cloudy sunset in Massachusetts.
  • Using base image: Yes

Somerville

• Model: Quantum (v2)*

• Size: 1682 X 1249 (2.10 MP)

• Used settings:

  • Prompt: Cloudy sunset in Massachusetts.
  • Using base image: Yes

Streetlights, Headlights

• Model: PhotoReal

• Size: 1682 X 1249 (2.10 MP)

• Used settings:

  • Prompt: Cloudy sunset in Massachusetts.
  • Using base image: Yes

Just 4 hours from New York

• Model: Artistic

• Size: 1682 X 1249 (2.10 MP)

• Used settings:

  • Prompt: Cloudy sunset in Massachusetts.
  • Using base image: Yes

Truman show

• Model: Artistic

• Size: 1682 X 1249 (2.10 MP)

• Used settings:

  • Prompt: Cloudy sunset in Massachusetts.
  • Using base image: Yes

git-rebase (1)

• Model: PhotoReal

• Size: 1635 X 1285 (2.10 MP)

• Used settings:

  • Prompt: git-rebase - Reapply commits on top of another base tip If <branch> is specified, git rebase will perform an automatic git switch <branch> before doing anything else. Otherwise it remains on the current branch. If <upstream> is not specified, the upstream configured in branch.<name>.remote and branch.<name>.merge options will be used (see git- config(1) for details) and the --fork-point option is assumed. If you are currently not on any branch or if the current branch does not have a configured upstream, the rebase will abort.
  • Using base image: No
  • Aspect Ratio: landscape

man git-cherry-pick

• Model: Fusion*

• Size: 1161 X 903 (1.05 MP)

• Used settings:

  • Prompt: git-cherry-pick - Apply the changes introduced by some existing commits SYNOPSIS git cherry-pick [--edit] [-n] [-m <parent-number>] [-s] [-x] [--ff] [-S[<keyid>]] <commit>... git cherry-pick (--continue | --skip | --abort | --quit) DESCRIPTION Given one or more existing commits, apply the change each one introduces, recording a new commit for each. This requires your working tree to be clean (no modifications from the HEAD commit). When it is not obvious how to apply a change, the following happens: 1. The current branch and HEAD pointer stay at the last commit successfully made. 2. The CHERRY_PICK_HEAD ref is set to point at the commit that introduced the change that is difficult to apply. 3. Paths in which the change applied cleanly are updated both in the index file and in your working tree. 4. For conflicting paths, the index file records up to three versions, as described in the "TRUE MERGE" section of git-merge(1). The working tree files will include a description of the conflict bracketed by the usual conflict markers <<<<<<< and >>>>>>>. 5. No other modifications are made. See git-merge(1) for some hints on resolving such conflicts.
  • Using base image: No
  • Aspect Ratio: landscape

git-rebase (1)

• Model: PhotoReal

• Size: 1643 X 1278 (2.10 MP)

• Used settings:

  • Prompt: git-rebase - Reapply commits on top of another base tip If <branch> is specified, git rebase will perform an automatic git switch <branch> before doing anything else. Otherwise it remains on the current branch. If <upstream> is not specified, the upstream configured in branch <name>.remote and branch.<name>.merge options will be used (see git-config(1) for details) and the --fork-point option is assumed. If you are currently not on any branch or if the current branch does not have a configured upstream, the rebase will abort.All changes made by commits in the current branch but that are not in <upstream> are saved to a temporary area. This is the same set of commits that would be shown by git log <upstream>..HEAD; or by git log 'fork_point'..HEAD, if --fork-point is active (see the description on --fork-point below); or by git log HEAD, if the --root option is specified
  • Using base image: No
  • Aspect Ratio: landscape

git-rebase (1)

• Model: Fusion*

• Size: 1161 X 903 (1.05 MP)

• Used settings:

  • Prompt: git-rebase - Reapply commits on top of another base tip If <branch> is specified, git rebase will perform an automatic git switch <branch> before doing anything else. Otherwise it remains on the current branch. If <upstream> is not specified, the upstream configured in branch <name>.remote and branch.<name>.merge options will be used (see git-config(1) for details) and the --fork-point option is assumed. If you are currently not on any branch or if the current branch does not have a configured upstream, the rebase will abort.All changes made by commits in the current branch but that are not in <upstream> are saved to a temporary area. This is the same set of commits that would be shown by git log <upstream>..HEAD; or by git log 'fork_point'..HEAD, if --fork-point is active (see the description on --fork-point below); or by git log HEAD, if the --root option is specified
  • Using base image: No
  • Aspect Ratio: landscape

git-rebase

• Model: Fusion*

• Size: 1643 X 1278 (2.10 MP)

• Used settings:

  • Prompt: git-rebase - Reapply commits on top of another base tip If <branch> is specified, git rebase will perform an automatic git switch <branch> before doing anything else. Otherwise it remains on the current branch. If <upstream> is not specified, the upstream configured in branch <name>.remote and branch.<name>.merge options will be used (see git-config(1) for details) and the --fork-point option is assumed. If you are currently not on any branch or if the current branch does not have a configured upstream, the rebase will abort.All changes made by commits in the current branch but that are not in <upstream> are saved to a temporary area. This is the same set of commits that would be shown by git log <upstream>..HEAD; or by git log 'fork_point'..HEAD, if --fork-point is active (see the description on --fork-point below); or by git log HEAD, if the --root option is specified.The current branch is reset to <upstream>, or <newbase> if the --onto option was supplied. This has the exact same effect as git reset --hard <upstream> (or <newbase>). ORIG_HEAD is set to point at the tip of the branch before the reset.
  • Using base image: No
  • Aspect Ratio: landscape

git-rebase (1)

• Model: Fusion*

• Size: 1643 X 1278 (2.10 MP)

• Used settings:

  • Prompt: git-rebase - Reapply commits on top of another base tip If <branch> is specified, git rebase will perform an automatic git switch <branch> before doing anything else. Otherwise it remains on the current branch. If <upstream> is not specified, the upstream configured in branch <name>.remote and branch.<name>.merge options will be used (see git-config(1) for details) and the --fork-point option is assumed. If you are currently not on any branch or if the current branch does not have a configured upstream, the rebase will abort.All changes made by commits in the current branch but that are not in <upstream> are saved to a temporary area. This is the same set of commits that would be shown by git log <upstream>..HEAD; or by git log 'fork_point'..HEAD, if --fork-point is active (see the description on --fork-point below); or by git log HEAD, if the --root option is specified.The current branch is reset to <upstream>, or <newbase> if the --onto option was supplied. This has the exact same effect as git reset --hard <upstream> (or <newbase>). ORIG_HEAD is set to point at the tip of the branch before the reset.
  • Using base image: No
  • Aspect Ratio: landscape

Colorless green ideas.

• Model: Artistic

• Size: 1643 X 1278 (2.10 MP)

• Used settings:

  • Prompt: Colorless green ideas sleep furiously.
  • Using base image: No
  • Aspect Ratio: landscape