ocschwar

Just a monoid

• Type:

  • Text 2 Dream
  
  

• Used settings:

  • Prompt: A monad is just a monoid in the category of endofunctors.
  • Using base image: Yes (Effect strength - 60%)
  • Base image resolution: Default
  • Quality: High Quality
  • Face enhance: No
  • Upscale & Enhance: 1
  • Aspect Ratio: landscape

Category theoretical

• Type:

  • Text 2 Dream
  
  

• Used settings:

  • Prompt: A monad is just a monoid in the category of endofunctors.
  • Using base image: Yes (Effect strength - 60%)
  • Base image resolution: Default
  • Quality: High Quality
  • Face enhance: No
  • Upscale & Enhance: 2
  • Aspect Ratio: landscape

The state of the world

• Type:

  • Text 2 Dream
  
  

• Used settings:

  • Prompt: A clown holding a flamethrower
  • Quality: Normal
  • Face enhance: No
  • Upscale & Enhance: 0
  • Aspect Ratio: landscape

A clown with a flamethrower

• Type:

  • Text 2 Dream
  
  

• Used settings:

  • Prompt: A clown holding a flamethrower
  • Quality: Normal
  • Face enhance: No
  • Upscale & Enhance: 0
  • Aspect Ratio: landscape

Category Theory.

• Type:

  • Text 2 Dream
  
  

• Used settings:

  • Prompt: A monad is just a monoid in the category of endofunctors.
  • Using base image: Yes (Effect strength - 60%)
  • Base image resolution: Default
  • Quality: High Quality
  • Face enhance: No
  • Upscale & Enhance: 2
  • Aspect Ratio: landscape

Category Theory

• Type:

  • Text 2 Dream
  
  

• Used settings:

  • Prompt: A monad is just a monoid in the category of endofunctors.
  • Using base image: Yes (Effect strength - 60%)
  • Base image resolution: Default
  • Quality: High Quality
  • Face enhance: No
  • Upscale & Enhance: 2
  • Aspect Ratio: landscape

git-rebase (1)

• Type:

  • Text 2 Dream
  
  

• 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.
  • Quality: High Quality
  • Face enhance: No
  • Upscale & Enhance: 2
  • Aspect Ratio: landscape

git-rebase

• Type:

  • Text 2 Dream
  
  

• 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.
  • Quality: High Quality
  • Face enhance: No
  • Upscale & Enhance: 2
  • Aspect Ratio: landscape

git-gc

• Type:

  • Text 2 Dream
  
  

• Used settings:

  • Prompt: git-gc - Cleanup unnecessary files and optimize the local repositorySYNOPSIS git gc [--aggressive] [--auto] [--quiet] [--prune=<date> | --no-prune] [--force] [--keep-largest-pack]DESCRIPTION Runs a number of housekeeping tasks within the current repository, such as compressing file revisions (to reduce disk space and increase performance), removing unreachable objects which may have been created from prior invocations of git add, packing refs, pruning reflog, rerere metadata or stale working trees. May also update ancillary indexes such as the commit-graph. When common porcelain operations that create objects are run, they will check whether the repository has grown substantially since the last maintenance, and if so run git gc automatically. See gc.auto below for how to disable this behavior. Running git gc manually should only be needed when adding objects to a repository without regularly running such porcelain commands, to do a one-off repository optimization, or e.g. to clean up a suboptimal mass-import. See the "PACKFILE OPTIMIZATION" section in git-fast-import(1) for more details on the import case. OPTIONS --aggressive Usually git gc runs very qui
  • Quality: High Quality
  • Face enhance: No
  • Upscale & Enhance: 2
  • Aspect Ratio: landscape

git-rebase

• Type:

  • Text 2 Dream
  
  

• 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.
  • Quality: High Quality
  • Face enhance: No
  • Upscale & Enhance: 2
  • Aspect Ratio: landscape

git-cherry-pick (1)

• Type:

  • Text 2 Dream
  
  

• 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.
  • Quality: High Quality
  • Face enhance: No
  • Upscale & Enhance: 1
  • Aspect Ratio: landscape

git-rebase (1)

• Type:

  • Text 2 Dream
  
  

• 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
  • Quality: High Quality
  • Face enhance: No
  • Upscale & Enhance: 1
  • Aspect Ratio: landscape

git-rebase (1)

• Type:

  • Text 2 Dream
  
  

• 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
  • Quality: High Quality
  • Face enhance: No
  • Upscale & Enhance: 2
  • Aspect Ratio: landscape

man git-cherry-pick

• Type:

  • Text 2 Dream
  
  

• 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.
  • Quality: High Quality
  • Face enhance: No
  • Upscale & Enhance: 1
  • Aspect Ratio: landscape