logo

oasis-root

Compiled tree of Oasis Linux based on own branch at <https://hacktivis.me/git/oasis/> git clone https://anongit.hacktivis.me/git/oasis-root.git

git-stash.1 (18190B)


  1. '\" t
  2. .\" Title: git-stash
  3. .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
  4. .\" Generator: DocBook XSL Stylesheets v1.79.2 <http://docbook.sf.net/>
  5. .\" Date: 2025-03-14
  6. .\" Manual: Git Manual
  7. .\" Source: Git 2.49.0
  8. .\" Language: English
  9. .\"
  10. .TH "GIT\-STASH" "1" "2025-03-14" "Git 2\&.49\&.0" "Git Manual"
  11. .\" -----------------------------------------------------------------
  12. .\" * Define some portability stuff
  13. .\" -----------------------------------------------------------------
  14. .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  15. .\" http://bugs.debian.org/507673
  16. .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
  17. .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  18. .ie \n(.g .ds Aq \(aq
  19. .el .ds Aq '
  20. .\" -----------------------------------------------------------------
  21. .\" * set default formatting
  22. .\" -----------------------------------------------------------------
  23. .\" disable hyphenation
  24. .nh
  25. .\" disable justification (adjust text to left margin only)
  26. .ad l
  27. .\" -----------------------------------------------------------------
  28. .\" * MAIN CONTENT STARTS HERE *
  29. .\" -----------------------------------------------------------------
  30. .SH "NAME"
  31. git-stash \- Stash the changes in a dirty working directory away
  32. .SH "SYNOPSIS"
  33. .sp
  34. .nf
  35. \fIgit stash\fR list [<log\-options>]
  36. \fIgit stash\fR show [\-u | \-\-include\-untracked | \-\-only\-untracked] [<diff\-options>] [<stash>]
  37. \fIgit stash\fR drop [\-q | \-\-quiet] [<stash>]
  38. \fIgit stash\fR pop [\-\-index] [\-q | \-\-quiet] [<stash>]
  39. \fIgit stash\fR apply [\-\-index] [\-q | \-\-quiet] [<stash>]
  40. \fIgit stash\fR branch <branchname> [<stash>]
  41. \fIgit stash\fR [push [\-p | \-\-patch] [\-S | \-\-staged] [\-k | \-\-[no\-]keep\-index] [\-q | \-\-quiet]
  42. [\-u | \-\-include\-untracked] [\-a | \-\-all] [(\-m | \-\-message) <message>]
  43. [\-\-pathspec\-from\-file=<file> [\-\-pathspec\-file\-nul]]
  44. [\-\-] [<pathspec>\&...\:]]
  45. \fIgit stash\fR save [\-p | \-\-patch] [\-S | \-\-staged] [\-k | \-\-[no\-]keep\-index] [\-q | \-\-quiet]
  46. [\-u | \-\-include\-untracked] [\-a | \-\-all] [<message>]
  47. \fIgit stash\fR clear
  48. \fIgit stash\fR create [<message>]
  49. \fIgit stash\fR store [(\-m | \-\-message) <message>] [\-q | \-\-quiet] <commit>
  50. .fi
  51. .SH "DESCRIPTION"
  52. .sp
  53. Use \fBgit\fR \fBstash\fR when you want to record the current state of the working directory and the index, but want to go back to a clean working directory\&. The command saves your local modifications away and reverts the working directory to match the \fBHEAD\fR commit\&.
  54. .sp
  55. The modifications stashed away by this command can be listed with \fBgit\fR \fBstash\fR \fBlist\fR, inspected with \fBgit\fR \fBstash\fR \fBshow\fR, and restored (potentially on top of a different commit) with \fBgit\fR \fBstash\fR \fBapply\fR\&. Calling \fBgit\fR \fBstash\fR without any arguments is equivalent to \fBgit\fR \fBstash\fR \fBpush\fR\&. A stash is by default listed as "WIP on \fIbranchname\fR \&...\:", but you can give a more descriptive message on the command line when you create one\&.
  56. .sp
  57. The latest stash you created is stored in \fBrefs/stash\fR; older stashes are found in the reflog of this reference and can be named using the usual reflog syntax (e\&.g\&. \fBstash@\fR{0} is the most recently created stash, \fBstash@\fR{1} is the one before it, \fBstash@\fR{2\&.\fBhours\&.ago\fR} is also possible)\&. Stashes may also be referenced by specifying just the stash index (e\&.g\&. the integer \fBn\fR is equivalent to \fBstash@\fR{n})\&.
  58. .SH "COMMANDS"
  59. .PP
  60. push [\-p|\-\-patch] [\-S|\-\-staged] [\-k|\-\-[no\-]keep\-index] [\-u|\-\-include\-untracked] [\-a|\-\-all] [\-q|\-\-quiet] [(\-m|\-\-message) <message>] [\-\-pathspec\-from\-file=<file> [\-\-pathspec\-file\-nul]] [\-\-] [<pathspec>\&...\:]
  61. .RS 4
  62. Save your local modifications to a new
  63. \fIstash entry\fR
  64. and roll them back to HEAD (in the working tree and in the index)\&. The <message> part is optional and gives the description along with the stashed state\&.
  65. .sp
  66. For quickly making a snapshot, you can omit "push"\&. In this mode, non\-option arguments are not allowed to prevent a misspelled subcommand from making an unwanted stash entry\&. The two exceptions to this are
  67. \fBstash\fR
  68. \fB\-p\fR
  69. which acts as alias for
  70. \fBstash\fR
  71. \fBpush\fR
  72. \fB\-p\fR
  73. and pathspec elements, which are allowed after a double hyphen
  74. \fB\-\-\fR
  75. for disambiguation\&.
  76. .RE
  77. .PP
  78. save [\-p|\-\-patch] [\-S|\-\-staged] [\-k|\-\-[no\-]keep\-index] [\-u|\-\-include\-untracked] [\-a|\-\-all] [\-q|\-\-quiet] [<message>]
  79. .RS 4
  80. This option is deprecated in favour of
  81. \fIgit stash push\fR\&. It differs from "stash push" in that it cannot take pathspec\&. Instead, all non\-option arguments are concatenated to form the stash message\&.
  82. .RE
  83. .PP
  84. list [<log\-options>]
  85. .RS 4
  86. List the stash entries that you currently have\&. Each
  87. \fIstash entry\fR
  88. is listed with its name (e\&.g\&.
  89. \fBstash@\fR{0} is the latest entry,
  90. \fBstash@\fR{1} is the one before, etc\&.), the name of the branch that was current when the entry was made, and a short description of the commit the entry was based on\&.
  91. .sp
  92. .if n \{\
  93. .RS 4
  94. .\}
  95. .nf
  96. stash@{0}: WIP on submit: 6ebd0e2\&.\&.\&. Update git\-stash documentation
  97. stash@{1}: On master: 9cc0589\&.\&.\&. Add git\-stash
  98. .fi
  99. .if n \{\
  100. .RE
  101. .\}
  102. .sp
  103. The command takes options applicable to the
  104. \fIgit log\fR
  105. command to control what is shown and how\&. See
  106. \fBgit-log\fR(1)\&.
  107. .RE
  108. .PP
  109. show [\-u|\-\-include\-untracked|\-\-only\-untracked] [<diff\-options>] [<stash>]
  110. .RS 4
  111. Show the changes recorded in the stash entry as a diff between the stashed contents and the commit back when the stash entry was first created\&. By default, the command shows the diffstat, but it will accept any format known to
  112. \fIgit diff\fR
  113. (e\&.g\&.,
  114. \fBgit\fR
  115. \fBstash\fR
  116. \fBshow\fR
  117. \fB\-p\fR
  118. \fBstash@\fR{1} to view the second most recent entry in patch form)\&. If no
  119. \fI<diff\-option>\fR
  120. is provided, the default behavior will be given by the
  121. \fBstash\&.showStat\fR, and
  122. \fBstash\&.showPatch\fR
  123. config variables\&. You can also use
  124. \fBstash\&.showIncludeUntracked\fR
  125. to set whether
  126. \fB\-\-include\-untracked\fR
  127. is enabled by default\&.
  128. .RE
  129. .PP
  130. pop [\-\-index] [\-q|\-\-quiet] [<stash>]
  131. .RS 4
  132. Remove a single stashed state from the stash list and apply it on top of the current working tree state, i\&.e\&., do the inverse operation of
  133. \fBgit\fR
  134. \fBstash\fR
  135. \fBpush\fR\&. The working directory must match the index\&.
  136. .sp
  137. Applying the state can fail with conflicts; in this case, it is not removed from the stash list\&. You need to resolve the conflicts by hand and call
  138. \fBgit\fR
  139. \fBstash\fR
  140. \fBdrop\fR
  141. manually afterwards\&.
  142. .RE
  143. .PP
  144. apply [\-\-index] [\-q|\-\-quiet] [<stash>]
  145. .RS 4
  146. Like
  147. \fBpop\fR, but do not remove the state from the stash list\&. Unlike
  148. \fBpop\fR,
  149. \fI<stash>\fR
  150. may be any commit that looks like a commit created by
  151. \fBstash\fR
  152. \fBpush\fR
  153. or
  154. \fBstash\fR
  155. \fBcreate\fR\&.
  156. .RE
  157. .PP
  158. branch <branchname> [<stash>]
  159. .RS 4
  160. Creates and checks out a new branch named
  161. \fI<branchname>\fR
  162. starting from the commit at which the
  163. \fI<stash>\fR
  164. was originally created, applies the changes recorded in
  165. \fI<stash>\fR
  166. to the new working tree and index\&. If that succeeds, and
  167. \fI<stash>\fR
  168. is a reference of the form
  169. \fBstash@\fR{\fI<revision>\fR}, it then drops the
  170. \fI<stash>\fR\&.
  171. .sp
  172. This is useful if the branch on which you ran
  173. \fBgit\fR
  174. \fBstash\fR
  175. \fBpush\fR
  176. has changed enough that
  177. \fBgit\fR
  178. \fBstash\fR
  179. \fBapply\fR
  180. fails due to conflicts\&. Since the stash entry is applied on top of the commit that was HEAD at the time
  181. \fBgit\fR
  182. \fBstash\fR
  183. was run, it restores the originally stashed state with no conflicts\&.
  184. .RE
  185. .PP
  186. clear
  187. .RS 4
  188. Remove all the stash entries\&. Note that those entries will then be subject to pruning, and may be impossible to recover (see
  189. \fIExamples\fR
  190. below for a possible strategy)\&.
  191. .RE
  192. .PP
  193. drop [\-q|\-\-quiet] [<stash>]
  194. .RS 4
  195. Remove a single stash entry from the list of stash entries\&.
  196. .RE
  197. .PP
  198. create
  199. .RS 4
  200. Create a stash entry (which is a regular commit object) and return its object name, without storing it anywhere in the ref namespace\&. This is intended to be useful for scripts\&. It is probably not the command you want to use; see "push" above\&.
  201. .RE
  202. .PP
  203. store
  204. .RS 4
  205. Store a given stash created via
  206. \fIgit stash create\fR
  207. (which is a dangling merge commit) in the stash ref, updating the stash reflog\&. This is intended to be useful for scripts\&. It is probably not the command you want to use; see "push" above\&.
  208. .RE
  209. .SH "OPTIONS"
  210. .PP
  211. \-a, \-\-all
  212. .RS 4
  213. This option is only valid for
  214. \fBpush\fR
  215. and
  216. \fBsave\fR
  217. commands\&.
  218. .sp
  219. All ignored and untracked files are also stashed and then cleaned up with
  220. \fBgit\fR
  221. \fBclean\fR\&.
  222. .RE
  223. .PP
  224. \-u, \-\-include\-untracked, \-\-no\-include\-untracked
  225. .RS 4
  226. When used with the
  227. \fBpush\fR
  228. and
  229. \fBsave\fR
  230. commands, all untracked files are also stashed and then cleaned up with
  231. \fBgit\fR
  232. \fBclean\fR\&.
  233. .sp
  234. When used with the
  235. \fBshow\fR
  236. command, show the untracked files in the stash entry as part of the diff\&.
  237. .RE
  238. .PP
  239. \-\-only\-untracked
  240. .RS 4
  241. This option is only valid for the
  242. \fBshow\fR
  243. command\&.
  244. .sp
  245. Show only the untracked files in the stash entry as part of the diff\&.
  246. .RE
  247. .PP
  248. \-\-index
  249. .RS 4
  250. This option is only valid for
  251. \fBpop\fR
  252. and
  253. \fBapply\fR
  254. commands\&.
  255. .sp
  256. Tries to reinstate not only the working tree\(cqs changes, but also the index\(cqs ones\&. However, this can fail, when you have conflicts (which are stored in the index, where you therefore can no longer apply the changes as they were originally)\&.
  257. .RE
  258. .PP
  259. \-k, \-\-keep\-index, \-\-no\-keep\-index
  260. .RS 4
  261. This option is only valid for
  262. \fBpush\fR
  263. and
  264. \fBsave\fR
  265. commands\&.
  266. .sp
  267. All changes already added to the index are left intact\&.
  268. .RE
  269. .PP
  270. \-p, \-\-patch
  271. .RS 4
  272. This option is only valid for
  273. \fBpush\fR
  274. and
  275. \fBsave\fR
  276. commands\&.
  277. .sp
  278. Interactively select hunks from the diff between HEAD and the working tree to be stashed\&. The stash entry is constructed such that its index state is the same as the index state of your repository, and its worktree contains only the changes you selected interactively\&. The selected changes are then rolled back from your worktree\&. See the
  279. \(lqInteractive Mode\(rq
  280. section of
  281. \fBgit-add\fR(1)
  282. to learn how to operate the
  283. \fB\-\-patch\fR
  284. mode\&.
  285. .sp
  286. The
  287. \fB\-\-patch\fR
  288. option implies
  289. \fB\-\-keep\-index\fR\&. You can use
  290. \fB\-\-no\-keep\-index\fR
  291. to override this\&.
  292. .RE
  293. .PP
  294. \-S, \-\-staged
  295. .RS 4
  296. This option is only valid for
  297. \fBpush\fR
  298. and
  299. \fBsave\fR
  300. commands\&.
  301. .sp
  302. Stash only the changes that are currently staged\&. This is similar to basic
  303. \fBgit\fR
  304. \fBcommit\fR
  305. except the state is committed to the stash instead of current branch\&.
  306. .sp
  307. The
  308. \fB\-\-patch\fR
  309. option has priority over this one\&.
  310. .RE
  311. .PP
  312. \-\-pathspec\-from\-file=<file>
  313. .RS 4
  314. This option is only valid for
  315. \fBpush\fR
  316. command\&.
  317. .sp
  318. Pathspec is passed in
  319. \fI<file>\fR
  320. instead of commandline args\&. If
  321. \fI<file>\fR
  322. is exactly
  323. \fB\-\fR
  324. then standard input is used\&. Pathspec elements are separated by LF or CR/LF\&. Pathspec elements can be quoted as explained for the configuration variable
  325. \fBcore\&.quotePath\fR
  326. (see
  327. \fBgit-config\fR(1))\&. See also
  328. \fB\-\-pathspec\-file\-nul\fR
  329. and global
  330. \fB\-\-literal\-pathspecs\fR\&.
  331. .RE
  332. .PP
  333. \-\-pathspec\-file\-nul
  334. .RS 4
  335. This option is only valid for
  336. \fBpush\fR
  337. command\&.
  338. .sp
  339. Only meaningful with
  340. \fB\-\-pathspec\-from\-file\fR\&. Pathspec elements are separated with NUL character and all other characters are taken literally (including newlines and quotes)\&.
  341. .RE
  342. .PP
  343. \-q, \-\-quiet
  344. .RS 4
  345. This option is only valid for
  346. \fBapply\fR,
  347. \fBdrop\fR,
  348. \fBpop\fR,
  349. \fBpush\fR,
  350. \fBsave\fR,
  351. \fBstore\fR
  352. commands\&.
  353. .sp
  354. Quiet, suppress feedback messages\&.
  355. .RE
  356. .PP
  357. \-\-
  358. .RS 4
  359. This option is only valid for
  360. \fBpush\fR
  361. command\&.
  362. .sp
  363. Separates pathspec from options for disambiguation purposes\&.
  364. .RE
  365. .PP
  366. <pathspec>\&...\:
  367. .RS 4
  368. This option is only valid for
  369. \fBpush\fR
  370. command\&.
  371. .sp
  372. The new stash entry records the modified states only for the files that match the pathspec\&. The index entries and working tree files are then rolled back to the state in HEAD only for these files, too, leaving files that do not match the pathspec intact\&.
  373. .sp
  374. For more details, see the
  375. \fIpathspec\fR
  376. entry in
  377. \fBgitglossary\fR(7)\&.
  378. .RE
  379. .PP
  380. <stash>
  381. .RS 4
  382. This option is only valid for
  383. \fBapply\fR,
  384. \fBbranch\fR,
  385. \fBdrop\fR,
  386. \fBpop\fR,
  387. \fBshow\fR
  388. commands\&.
  389. .sp
  390. A reference of the form
  391. \fBstash@\fR{\fI<revision>\fR}\&. When no
  392. \fI<stash>\fR
  393. is given, the latest stash is assumed (that is,
  394. \fBstash@\fR{0})\&.
  395. .RE
  396. .SH "DISCUSSION"
  397. .sp
  398. A stash entry is represented as a commit whose tree records the state of the working directory, and its first parent is the commit at \fBHEAD\fR when the entry was created\&. The tree of the second parent records the state of the index when the entry is made, and it is made a child of the \fBHEAD\fR commit\&. The ancestry graph looks like this:
  399. .sp
  400. .if n \{\
  401. .RS 4
  402. .\}
  403. .nf
  404. \&.\-\-\-\-W
  405. / /
  406. \-\-\-\-\-H\-\-\-\-I
  407. .fi
  408. .if n \{\
  409. .RE
  410. .\}
  411. .sp
  412. where \fBH\fR is the \fBHEAD\fR commit, \fBI\fR is a commit that records the state of the index, and \fBW\fR is a commit that records the state of the working tree\&.
  413. .SH "EXAMPLES"
  414. .PP
  415. Pulling into a dirty tree
  416. .RS 4
  417. When you are in the middle of something, you learn that there are upstream changes that are possibly relevant to what you are doing\&. When your local changes do not conflict with the changes in the upstream, a simple
  418. \fBgit\fR
  419. \fBpull\fR
  420. will let you move forward\&.
  421. .sp
  422. However, there are cases in which your local changes do conflict with the upstream changes, and
  423. \fBgit\fR
  424. \fBpull\fR
  425. refuses to overwrite your changes\&. In such a case, you can stash your changes away, perform a pull, and then unstash, like this:
  426. .sp
  427. .if n \{\
  428. .RS 4
  429. .\}
  430. .nf
  431. $ git pull
  432. \&.\&.\&.
  433. file foobar not up to date, cannot merge\&.
  434. $ git stash
  435. $ git pull
  436. $ git stash pop
  437. .fi
  438. .if n \{\
  439. .RE
  440. .\}
  441. .RE
  442. .PP
  443. Interrupted workflow
  444. .RS 4
  445. When you are in the middle of something, your boss comes in and demands that you fix something immediately\&. Traditionally, you would make a commit to a temporary branch to store your changes away, and return to your original branch to make the emergency fix, like this:
  446. .sp
  447. .if n \{\
  448. .RS 4
  449. .\}
  450. .nf
  451. # \&.\&.\&. hack hack hack \&.\&.\&.
  452. $ git switch \-c my_wip
  453. $ git commit \-a \-m "WIP"
  454. $ git switch master
  455. $ edit emergency fix
  456. $ git commit \-a \-m "Fix in a hurry"
  457. $ git switch my_wip
  458. $ git reset \-\-soft HEAD^
  459. # \&.\&.\&. continue hacking \&.\&.\&.
  460. .fi
  461. .if n \{\
  462. .RE
  463. .\}
  464. .sp
  465. You can use
  466. \fIgit stash\fR
  467. to simplify the above, like this:
  468. .sp
  469. .if n \{\
  470. .RS 4
  471. .\}
  472. .nf
  473. # \&.\&.\&. hack hack hack \&.\&.\&.
  474. $ git stash
  475. $ edit emergency fix
  476. $ git commit \-a \-m "Fix in a hurry"
  477. $ git stash pop
  478. # \&.\&.\&. continue hacking \&.\&.\&.
  479. .fi
  480. .if n \{\
  481. .RE
  482. .\}
  483. .RE
  484. .PP
  485. Testing partial commits
  486. .RS 4
  487. You can use
  488. \fBgit\fR
  489. \fBstash\fR
  490. \fBpush\fR
  491. \fB\-\-keep\-index\fR
  492. when you want to make two or more commits out of the changes in the work tree, and you want to test each change before committing:
  493. .sp
  494. .if n \{\
  495. .RS 4
  496. .\}
  497. .nf
  498. # \&.\&.\&. hack hack hack \&.\&.\&.
  499. $ git add \-\-patch foo # add just first part to the index
  500. $ git stash push \-\-keep\-index # save all other changes to the stash
  501. $ edit/build/test first part
  502. $ git commit \-m \*(AqFirst part\*(Aq # commit fully tested change
  503. $ git stash pop # prepare to work on all other changes
  504. # \&.\&.\&. repeat above five steps until one commit remains \&.\&.\&.
  505. $ edit/build/test remaining parts
  506. $ git commit foo \-m \*(AqRemaining parts\*(Aq
  507. .fi
  508. .if n \{\
  509. .RE
  510. .\}
  511. .RE
  512. .PP
  513. Saving unrelated changes for future use
  514. .RS 4
  515. When you are in the middle of massive changes and you find some unrelated issue that you don\(cqt want to forget to fix, you can do the change(s), stage them, and use
  516. \fBgit\fR
  517. \fBstash\fR
  518. \fBpush\fR
  519. \fB\-\-staged\fR
  520. to stash them out for future use\&. This is similar to committing the staged changes, only the commit ends\-up being in the stash and not on the current branch\&.
  521. .sp
  522. .if n \{\
  523. .RS 4
  524. .\}
  525. .nf
  526. # \&.\&.\&. hack hack hack \&.\&.\&.
  527. $ git add \-\-patch foo # add unrelated changes to the index
  528. $ git stash push \-\-staged # save these changes to the stash
  529. # \&.\&.\&. hack hack hack, finish current changes \&.\&.\&.
  530. $ git commit \-m \*(AqMassive\*(Aq # commit fully tested changes
  531. $ git switch fixup\-branch # switch to another branch
  532. $ git stash pop # to finish work on the saved changes
  533. .fi
  534. .if n \{\
  535. .RE
  536. .\}
  537. .RE
  538. .PP
  539. Recovering stash entries that were cleared/dropped erroneously
  540. .RS 4
  541. If you mistakenly drop or clear stash entries, they cannot be recovered through the normal safety mechanisms\&. However, you can try the following incantation to get a list of stash entries that are still in your repository, but not reachable any more:
  542. .sp
  543. .if n \{\
  544. .RS 4
  545. .\}
  546. .nf
  547. git fsck \-\-unreachable |
  548. grep commit | cut \-d\e \-f3 |
  549. xargs git log \-\-merges \-\-no\-walk \-\-grep=WIP
  550. .fi
  551. .if n \{\
  552. .RE
  553. .\}
  554. .RE
  555. .SH "CONFIGURATION"
  556. .sp
  557. Everything below this line in this section is selectively included from the \fBgit-config\fR(1) documentation\&. The content is the same as what\(cqs found there:
  558. .PP
  559. stash\&.showIncludeUntracked
  560. .RS 4
  561. If this is set to true, the
  562. \fBgit\fR
  563. \fBstash\fR
  564. \fBshow\fR
  565. command will show the untracked files of a stash entry\&. Defaults to false\&. See the description of the
  566. \fIshow\fR
  567. command in
  568. \fBgit-stash\fR(1)\&.
  569. .RE
  570. .PP
  571. stash\&.showPatch
  572. .RS 4
  573. If this is set to true, the
  574. \fBgit\fR
  575. \fBstash\fR
  576. \fBshow\fR
  577. command without an option will show the stash entry in patch form\&. Defaults to false\&. See the description of the
  578. \fIshow\fR
  579. command in
  580. \fBgit-stash\fR(1)\&.
  581. .RE
  582. .PP
  583. stash\&.showStat
  584. .RS 4
  585. If this is set to true, the
  586. \fBgit\fR
  587. \fBstash\fR
  588. \fBshow\fR
  589. command without an option will show a diffstat of the stash entry\&. Defaults to true\&. See the description of the
  590. \fIshow\fR
  591. command in
  592. \fBgit-stash\fR(1)\&.
  593. .RE
  594. .SH "SEE ALSO"
  595. .sp
  596. \fBgit-checkout\fR(1), \fBgit-commit\fR(1), \fBgit-reflog\fR(1), \fBgit-reset\fR(1), \fBgit-switch\fR(1)
  597. .SH "GIT"
  598. .sp
  599. Part of the \fBgit\fR(1) suite