On Sun, Apr 16, 2017 at 11:25 AM, Duy Nguyen wrote:
>> Because this is a reset --mixed it will never run through unpack_trees and
>> The entries are never marked with CE_REMOVE.
>
> I know. But in my view, it should. All updates from a tree object to
> the index should happen through unpack_trees(
c: Kevin Willford ; git@vger.kernel.org;
>> gits...@pobox.com; p...@peff.net
>> Subject: Re: [PATCH 3/3] reset.c: update files when using sparse to avoid
>> data loss.
>>
>> On Wed, Apr 12, 2017 at 5:30 AM, Kevin Willford
>> wrote:
>> > The loss of the sk
Subject: Re: [PATCH 3/3] reset.c: update files when using sparse to avoid
> data loss.
>
> On Wed, Apr 12, 2017 at 5:30 AM, Kevin Willford
> wrote:
> > The loss of the skip-worktree bits is part of the problem if you are
> > talking about modified files. The other issue t
On Wed, Apr 12, 2017 at 5:30 AM, Kevin Willford wrote:
> The loss of the skip-worktree bits is part of the problem if you are talking
> about modified files. The other issue that I was having is when running a
> reset
> and there were files added in the commit that is being reset, there will not
> -Original Message-
> From: Duy Nguyen [mailto:pclo...@gmail.com]
> Sent: Monday, April 10, 2017 4:24 AM
> To: Kevin Willford
> Cc: git@vger.kernel.org; gits...@pobox.com; p...@peff.net; Kevin Willford
>
> Subject: Re: [PATCH 3/3] reset.c: update files when using s
On Fri, Apr 07, 2017 at 12:23:57PM -0700, Kevin Willford wrote:
> When using the sparse checkout feature the git reset command will add
"git reset" has three different modes. It would be good if you mention
what mode is affected here. The tests are for --mixed only. I wonder
if we need to do anyth
On Fri, Apr 7, 2017 at 12:23 PM, Kevin Willford wrote:
> When using the sparse checkout feature the git reset command will add
> entries to the index that will have the skip-worktree bit off but will
> leave the working directory empty. File data is lost because the index
> version of the files h
7 matches
Mail list logo