git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] unpack-trees: do not fail reset because of unmerged skipped entry

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 11, 2018, 16:35 UTC
Message-ID
<xmqq1sc94tn4.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<CACsJy8BVadBd1T2yoUhnxd21=c8SVaFqPXT8kk4NfnzGyBNOCw@mail.gmail.com>
Duy Nguyen <pclouds@gmail.com> writes:
Show 22 quoted lines
> On Tue, Jul 10, 2018 at 9:22 PM Max Kirillov <max@max630.net> wrote:
>>
>> On Sat, Jun 16, 2018 at 07:14:44AM +0200, Duy Nguyen wrote:
>> > -- 8< --
>> > diff --git a/unpack-trees.c b/unpack-trees.c
>> > index 3a85a02a77..eb544ee1b3 100644
>> > --- a/unpack-trees.c
>> > +++ b/unpack-trees.c
>> > @@ -1246,7 +1246,7 @@ static void mark_new_skip_worktree(struct exclude_list *el,
>> >               if (select_flag && !(ce->ce_flags & select_flag))
>> >                       continue;
>> >
>> > -             if (!ce_stage(ce))
>> > +             if (!ce_stage(ce) && !(ce->ce_flags & CE_CONFLICTED))
>> >                       ce->ce_flags |= skip_wt_flag;
>> >               else
>> >                       ce->ce_flags &= ~skip_wt_flag;
>> > -- 8< --
>>
>> I tried your fix and it is working. I put it instead of my original fix. Would you sign it off?
>
> Signed-off-by: Duy Nguyen <pclouds@gmail.com>
Thanks, both.
Previous: Duy NguyenNext: Max Kirillov
Message 8 of 9 in “unpack-trees: do not fail reset because of unmerged skipped entry”
  1. unpack-trees: do not fail reset because of unmerged skipped entryMax Kirillov, Jun 15, 2018
  2. Junio C HamanoJun 15, 2018
  3. Max KirillovJun 16, 2018
  4. Max KirillovJul 10, 2018
  5. Duy NguyenJun 16, 2018
  6. Max KirillovJul 10, 2018
  7. Duy NguyenJul 11, 2018
  8. Junio C HamanoJul 11, 2018
  9. unpack-trees: do not fail reset because of unmerged skipped entryMax Kirillov, Jul 10, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.