Signed-off-by: Yann Dirson <ydirson@altern.org>
---
Well, it looks like the voices we heard on this naming issue were
quite equally cast towards each of the 2 name.
Let my vote be to get back to "sink", so the user can easily pair the
command with "float". I expect that any previously-silent majoity
prefering "bury" will talk now, before Catalin decides if he wants
this patch in the next release :)
Oh, this patch reminds me we still have to activate rename
detection...
Documentation/stg-bury.txt | 49 -------------------------------
Documentation/stg-sink.txt | 49 +++++++++++++++++++++++++++++++
Documentation/stg.txt | 4 +--
contrib/stgit-completion.bash | 4 +--
stgit/commands/bury.py | 65 -----------------------------------------
stgit/commands/sink.py | 65 +++++++++++++++++++++++++++++++++++++++++
stgit/main.py | 4 +--
7 files changed, 120 insertions(+), 120 deletions(-)
diff --git a/Documentation/stg-bury.txt b/Documentation/stg-bury.txt
deleted file mode 100644
index 22ab548..0000000
--- a/Documentation/stg-bury.txt
+++ /dev/null
@@ -1,49 +0,0 @@
-stg-bury(1)
-===========
-Yann Dirson <ydirson@altern.org>
-v0.13, April 2007
-
-NAME
-----
-stg-bury - stgdesc:bury[]
-
-SYNOPSIS
---------
-[verse]
-'stg' bury [--to=<target>] [--nopush] [<patches>]
-
-DESCRIPTION
------------
-
-This is the opposite operation of stglink:float[]: move the specified
-patches down the stack. It is for example useful to group stable
-patches near the bottom of the stack, where they are less likely to be
-impacted by the push of another patch, and from where they can be more
-easily committed or pushed.
-
-If no patch is specified on command-line, the current patch is buried.
-By default patches are buried at the bottom of the stack, but the
-'--to' option allows to bury under any applied patch.
-
-Buring internally involves popping all patches (or all patches
-including <targ...