Commit | Line | Data |
---|---|---|
6f1c5e3c | 1 | stg-sink(1) |
de7a79c4 YD |
2 | =========== |
3 | Yann Dirson <ydirson@altern.org> | |
4 | v0.13, April 2007 | |
5 | ||
6 | NAME | |
7 | ---- | |
6f1c5e3c | 8 | stg-sink - stgdesc:sink[] |
de7a79c4 YD |
9 | |
10 | SYNOPSIS | |
11 | -------- | |
12 | [verse] | |
6f1c5e3c | 13 | 'stg' sink [--to=<target>] [--nopush] [<patches>] |
de7a79c4 YD |
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 | ||
6f1c5e3c YD |
24 | If no patch is specified on command-line, the current patch gets sunk. |
25 | By default patches are sunk to the bottom of the stack, but the | |
26 | '--to' option allows to place them under any applied patch. | |
de7a79c4 | 27 | |
6f1c5e3c YD |
28 | Sinking internally involves popping all patches (or all patches |
29 | including <target patch>), then pushing the patches to sink, and then | |
de7a79c4 YD |
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>:: | |
6f1c5e3c YD |
39 | Specify a target patch to place the patches below, instead of |
40 | sinking them to the bottom of the stack. | |
de7a79c4 YD |
41 | |
42 | --nopush:: | |
43 | -n:: | |
44 | Do not push back on the stack the formerly-applied patches. | |
6f1c5e3c | 45 | Only the patches to sink are pushed. |
de7a79c4 YD |
46 | |
47 | StGIT | |
48 | ----- | |
49 | Part of the StGIT suite - see gitlink:stg[1]. |