"local_mode" and "no_commits" options for "new" command

[Oleg Sharov]

2007/1/24, Vlad Skvortsov <vss at 73rus.com>:
>
> Иван Глушков wrote:
> > Hi.
> > A question about the issue #85 (about adding "local_mode" option).
> >
> > I've discovered that option "no_commits" has the same meaning for the
> > "new" command as "local_mode".
> > First i decided to remove it but then i supposed that it was good to
> > have the one option for this action (better to say "inaction") for all
> > commands.
> > So i saved it and now it's the synonym for "local_mode" option (only for
> "new").
> >
> > Your opinions?
> >
>
> Currently only 2 commands make use of '-l':
> 22:27 [vss at claw] ~/ditrack/src/trunk > find . -name "*.py" | xargs grep
> -n local_mode
> ./DITrack/Command/list.py:62: if opts.var["local_mode"]:
> ./DITrack/Command/new.py:110: if opts.var["local_mode"] or
> opts.var["no_commits"]:
>
>
> See also i#82.
>
> My feeling is that '-l' is not appropriate. Now we have the 'status'
> command to display local entities, so I'm actually leaning towards
> removing '-l' completely... Your opinions?


I agree with Vlad. We must have different options for
1. work with lma or wc
2. defining necessity of check in issues to a repository


-- 
Oleg G. Sharov
o.sharov at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ditrack.org/pipermail/dev/attachments/20070124/ab57733b/attachment.html