Re: StGIT: "stg new" vs "stg new --force"
- From
Karl Hasselström <kha@treskal.com>
- Date
- Jan 13, 2006, 09:34 UTC
- Message-ID
- <20060113093420.GA25242@diana.vm.bytemark.co.uk>
- In-Reply-To
- <1137144291.20073.104.camel@dv>
On 2006-01-13 04:24:51 -0500, Pavel Roskin wrote:
Show 6 quoted lines
> 1) "stg new --force" becomes "stg new" and "stg new" becomes "stg new > --empty", i.e. empty files can only be created with the "--empty" > switch. > 2) "stg new --force" becomes "stg record" or something. > 3) "stg new --force" becomes "stg new --record" or something. > 4) "stg new" works both with and without modified files.
I agree with Pavel. I like option 4 the most, and 3 the least; since creating a new patch from existing edits is more common (for me) than creating an empty patch, it's awkward to make that command much longer.
--
Karl Hasselström, kha@treskal.com
www.treskal.com/kalle