~mdw / stgit / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 15de5ae) | patch
Remove the --force option for new
authorCatalin Marinas <catalin.marinas@gmail.com>
Sun, 22 Jan 2006 08:56:24 +0000 (08:56 +0000)
committerCatalin Marinas <catalin.marinas@gmail.com>
Sun, 22 Jan 2006 08:56:24 +0000 (08:56 +0000)
commit3bd6274e247baa8c9f652fcdfd74180b0933773c
tree61c1c75552bba8846d7e456fcdbb96208f999ee3tree | snapshot (tar.gz zip)
parent15de5ae14f1c76adac52ca5633a679fba79a877ccommit | diff
Remove the --force option for new

The default behaviour is now the same as the previous 'new --force' since
most of the people (and myself) first change the tree and run 'new'
afterwards to create the patch. Note that the newly created patch is empty
even if there are local changes. A 'refresh' command is needed to add the
local changes to the patch.

Signed-off-by: Catalin Marinas <catalin.marinas@gmail.com>
stgit/commands/new.py diff | blob | blame | history
GIT patch-maintenance porcelain (local modifications)