On Tue, Apr 11, 2017 at 4:11 PM, Thomas <tho...@dateiliste.com> wrote:
> On 2017-04-11 22:51, Scott Robison wrote:
>>
>> On Tue, Apr 11, 2017 at 3:39 PM, Scott Robison <sc...@casaderobison.com>
>> wrote:
>>>
>>> On Tue, Apr 11, 2017 at 3:21 PM, Thomas <tho...@dateiliste.com> wrote:
>>>>
>>>> On 2017-04-11 22:11, Thomas wrote:
>>>>
>>>> add
>>>> --ignore <CSG> Ignore unmanaged files matching
>>>> patterns from the comma separated list of
>>>> glob patterns.
>>>> --exclude <CSG> Exclude files matching patterns from
>>>> the comma separated list of glob patterns.
>>>>
>>>> The same for addremove, I guess.
>>>
>>>
>>> I've updated the documentation for --ignore for add and addremove.
>>> Adding exclude is more than I have time for at this moment. Baby
>>> steps.
>>
>>
>> I still think there is a fundamental misunderstanding about addremove.
>
>
> I think not a misunderstanding but I made a minor error. There's nothing
> wrong with the add command as it currently is. This --exclude would only
> apply to addremove because the add command has it already (= rm or delete).
{snipped}
Okay, so you *do* want (or at least expected) the use of --ignore (in
the context of addremove) to "rm" files already being managed. Which
is not an unreasonable desire, certainly could make some work flows
easier. The addremove command was structured around the idea of "this
unmanaged file that exists in the working directory should be added at
the next commit, and this managed file that no longer exists in the
woking directory should be removed at the next commit".
In any case, the "unmanaged files" text is a good addition to both, I
think, since add can be used to add the contents of a directory.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
