~mdw / stgit / blame
| Commit | Line | Data |
|---|---|---|
| de7a79c4 YD |
1 | stg-bury(1) |
| 2 | =========== | |
| 3 | Yann Dirson <ydirson@altern.org> | |
| 4 | v0.13, April 2007 | |
| 5 | ||
| 6 | NAME | |
| 7 | ---- | |
| 8 | stg-bury - stgdesc:bury[] | |
| 9 | ||
| 10 | SYNOPSIS | |
| 11 | -------- | |
| 12 | [verse] | |
| 13 | 'stg' bury [--to=<target>] [--nopush] [<patches>] | |
| 14 | ||
| 15 | DESCRIPTION | |
| 16 | ----------- | |
| 17 | ||
| 18 | This is the opposite operation of stglink:float[]: move the specified | |
| 19 | patches down the stack. It is for example useful to group stable | |
| 20 | patches near the bottom of the stack, where they are less likely to be | |
| 21 | impacted by the push of another patch, and from where they can be more | |
| 22 | easily committed or pushed. | |
| 23 | ||
| 24 | If no patch is specified on command-line, the current patch is buried. | |
| 25 | By default patches are buried at the bottom of the stack, but the | |
| 26 | '--to' option allows to bury under any applied patch. | |
| 27 | ||
| 28 | Buring internally involves popping all patches (or all patches | |
| 29 | including <target patch>), then pushing the patches to bury, and then | |
| 30 | (unless '--nopush' is also given) pushing back into place the | |
| 31 | formerly-applied patches. | |
| 32 | ||
| 33 | ||
| 34 | OPTIONS | |
| 35 | ------- | |
| 36 | ||
| 37 | --to=<TARGET>:: | |
| 38 | -t <TARGET>:: | |
| 39 | Specify a target patch to bury the patches below, instead of | |
| 40 | buring at the bottom of the stack. | |
| 41 | ||
| 42 | --nopush:: | |
| 43 | -n:: | |
| 44 | Do not push back on the stack the formerly-applied patches. | |
| 45 | Only the patches to bury are pushed. | |
| 46 | ||
| 47 | StGIT | |
| 48 | ----- | |
| 49 | Part of the StGIT suite - see gitlink:stg[1]. |