From: Don Zickus <dzickus@redhat.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Alexander Potashev <aspotashev@gmail.com>
Subject: Re: [PATCH] builtin-apply.c: do not set bogus mode in check_preimage() for deleted path
Date: Wed, 28 Jan 2009 20:46:20 -0500 [thread overview]
Message-ID: <20090129014620.GE13271@redhat.com> (raw)
In-Reply-To: <7vocxrj9j9.fsf@gitster.siamese.dyndns.org>
On Wed, Jan 28, 2009 at 03:27:54PM -0800, Junio C Hamano wrote:
> Also I suspect this codepath has been broken the use case 7a07841
> (git-apply: handle a patch that touches the same path more than once
> better, 2008-06-27) wanted to support, and if that is the case, this
> would fix it.
Actually deleting patches weren't that interesting to me, I deal more with
patches modifying the same patch repeatedly. Regardless the patch below
seems ok to me.
Acked-by: Don Zickus <dzickus@redhat.com>
>
> builtin-apply.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/builtin-apply.c b/builtin-apply.c
> index b415daf..1e7f917 100644
> --- a/builtin-apply.c
> +++ b/builtin-apply.c
> @@ -2453,7 +2453,7 @@ static int check_preimage(struct patch *patch, struct cache_entry **ce, struct s
> if (st_mode != patch->old_mode)
> fprintf(stderr, "warning: %s has type %o, expected %o\n",
> old_name, st_mode, patch->old_mode);
> - if (!patch->new_mode)
> + if (!patch->new_mode && !patch->is_delete)
> patch->new_mode = st_mode;
> return 0;
>
> --
> 1.6.1.1.278.g6a817
>
prev parent reply other threads:[~2009-01-29 1:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 23:27 [PATCH] builtin-apply.c: do not set bogus mode in check_preimage() for deleted path Junio C Hamano
2009-01-29 1:46 ` Don Zickus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090129014620.GE13271@redhat.com \
--to=dzickus@redhat.com \
--cc=aspotashev@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).