Re: kha/safe and kha/experimental updated
- From
Karl Hasselström <kha@treskal.com>
- Date
- Dec 19, 2007, 09:38 UTC
- Message-ID
- <20071219093816.GB4361@diana.vm.bytemark.co.uk>
- In-Reply-To
- <m3hcigot3h.fsf@roke.D-201>
On 2007-12-18 08:39:52 -0800, Jakub Narebski wrote:
Show 17 quoted lines
> "Catalin Marinas" <catalin.marinas@gmail.com> writes: > > > On 18/12/2007, Karl Hasselström <kha@treskal.com> wrote: > > > > > Remove "stg resolved" > > > > I'd like to keep this command. git-mergetool doesn't support the > > tool I use (emacs + ediff and more stgit-specific file extensions > > like current, patch etc.). I also don't find 'git add' to be > > meaningful for marking a conflict as solved. > > I also would like to have this command kept (and shown in 'stg > help'!). Contrary to 'git add' it can check and add to index / > update index only for files with conflict; we have -r > (ancestor|current|patched) to choose one side, and we could add > --check to check if there are no conflict markers with files (useful > with -a/--all).
This too sounds like stuff that could profitably be added to "git add". Except for the ancestor/current/patched words, it is not specific to patch stacks, so the implementation should be in git and not in stg.
IMHO, of course. :-)
--
Karl Hasselström, kha@treskal.com
www.treskal.com/kalle