> "Jonas Bang" writes:
>
> >> >> ... The default behaviour would cover their use case so your
> >> >> proposal would not hurt them, but I wonder if there are things you
> >> >> could do to help them as well, perhaps by allowing this new
> >> >> configuration to express something like "local chan
"Jonas Bang" writes:
>> >> ... The default behaviour would cover their
>> >> use case so your proposal would not hurt them, but I wonder if there
>> >> are things you could do to help them as well, perhaps by allowing
>> >> this new configuration to express something like "local changes in
>> >>
> >> For some people it is also a norm to keep files that have been
> >> modified from HEAD and/or index without committing for a long time
> >> (e.g. earlier, Linus said that the version in Makefile is updated and
> >> kept modified in the working tree long before a new release is
> >> committed w
"Jonas Bang" writes:
>> For some people it is also a norm to keep files that have been modified from
>> HEAD and/or index without committing for a long time (e.g. earlier, Linus
>> said
>> that the version in Makefile is updated and kept modified in the working tree
>> long before a new release
Thanks for your feedback, Junio, I have added more details and tried to
simplify the request.
> "Jonas Bang" writes:
>
> > Hi Git developers,
> >
> > This is my first Git feature request, I hope it won’t get me hanged on
> > the gallows ;o)
> >
> > *Git feature request:*
> > Add an option to Gi
"Jonas Bang" writes:
> Hi Git developers,
>
> This is my first Git feature request, I hope it won’t get me hanged on the
> gallows ;o)
>
> *Git feature request:*
> Add an option to Git config to configure the criteria for when a "git
> checkout" should abort.
>
> *Name proposal and options:*
>
6 matches
Mail list logo