From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 06/13] builtin-apply.c: mark common context lines in lineinfo structure.
Date: Sat, 2 Feb 2008 02:54:12 -0800 [thread overview]
Message-ID: <1201949659-27725-7-git-send-email-gitster@pobox.com> (raw)
In-Reply-To: <1201949659-27725-6-git-send-email-gitster@pobox.com>
This updates the way preimage and postimage in a patch hunk is
parsed and prepared for applying. By looking at image->line[n].flag,
the code can tell if it is a common context line that is the
same between the preimage and the postimage.
This matters when we actually start applying a patch with
contexts that have whitespace breakages that have already been
fixed in the target file.
---
builtin-apply.c | 57 ++++++++++++++++++++++++++++++------------------------
1 files changed, 32 insertions(+), 25 deletions(-)
diff --git a/builtin-apply.c b/builtin-apply.c
index dc650f1..acd84f9 100644
--- a/builtin-apply.c
+++ b/builtin-apply.c
@@ -170,6 +170,7 @@ struct line {
size_t len;
unsigned hash : 24;
unsigned flag : 8;
+#define LINE_COMMON 1
};
/*
@@ -179,6 +180,7 @@ struct image {
char *buf;
size_t len;
size_t nr;
+ size_t alloc;
struct line *line_allocated;
struct line *line;
};
@@ -195,49 +197,39 @@ static uint32_t hash_line(const char *cp, size_t len)
return h;
}
+static void add_line_info(struct image *img, const char *bol, size_t len, unsigned flag)
+{
+ ALLOC_GROW(img->line_allocated, img->nr + 1, img->alloc);
+ img->line_allocated[img->nr].len = len;
+ img->line_allocated[img->nr].hash = hash_line(bol, len);
+ img->line_allocated[img->nr].flag = flag;
+ img->nr++;
+}
+
static void prepare_image(struct image *image, char *buf, size_t len,
int prepare_linetable)
{
const char *cp, *ep;
- int n;
+ memset(image, 0, sizeof(*image));
image->buf = buf;
image->len = len;
- if (!prepare_linetable) {
- image->line = NULL;
- image->line_allocated = NULL;
- image->nr = 0;
+ if (!prepare_linetable)
return;
- }
ep = image->buf + image->len;
-
- /* First count lines */
cp = image->buf;
- n = 0;
- while (cp < ep) {
- cp = strchrnul(cp, '\n');
- n++;
- cp++;
- }
-
- image->line_allocated = xcalloc(n, sizeof(struct line));
- image->line = image->line_allocated;
- image->nr = n;
- cp = image->buf;
- n = 0;
while (cp < ep) {
const char *next;
for (next = cp; next < ep && *next != '\n'; next++)
;
if (next < ep)
next++;
- image->line[n].len = next - cp;
- image->line[n].hash = hash_line(cp, next - cp);
+ add_line_info(image, cp, next - cp, 0);
cp = next;
- n++;
}
+ image->line = image->line_allocated;
}
static void clear_image(struct image *image)
@@ -1822,6 +1814,9 @@ static int apply_one_fragment(struct image *img, struct fragment *frag,
struct image preimage;
struct image postimage;
+ memset(&preimage, 0, sizeof(preimage));
+ memset(&postimage, 0, sizeof(postimage));
+
while (size > 0) {
char first;
int len = linelen(patch, size);
@@ -1857,10 +1852,14 @@ static int apply_one_fragment(struct image *img, struct fragment *frag,
break;
old[oldsize++] = '\n';
new[newsize++] = '\n';
+ add_line_info(&preimage, "\n", 1, LINE_COMMON);
+ add_line_info(&postimage, "\n", 1, LINE_COMMON);
break;
case ' ':
case '-':
memcpy(old + oldsize, patch + 1, plen);
+ add_line_info(&preimage, old + oldsize, plen,
+ (first == ' ' ? LINE_COMMON : 0));
oldsize += plen;
if (first == '-')
break;
@@ -1869,6 +1868,9 @@ static int apply_one_fragment(struct image *img, struct fragment *frag,
if (first != '+' || !no_add) {
int added = apply_line(new + newsize, patch,
plen, ws_rule);
+ add_line_info(&postimage, new + newsize, added,
+ (first == '+' ? 0 : LINE_COMMON));
+
newsize += added;
if (first == '+' &&
added == 1 && new[newsize-1] == '\n')
@@ -1921,8 +1923,13 @@ static int apply_one_fragment(struct image *img, struct fragment *frag,
}
pos = frag->newpos ? (frag->newpos - 1) : 0;
- prepare_image(&preimage, oldlines, oldsize, 1);
- prepare_image(&postimage, newlines, newsize, 1);
+ preimage.buf = old;
+ preimage.len = oldsize;
+ postimage.buf = new;
+ postimage.len = newsize;
+ preimage.line = preimage.line_allocated;
+ postimage.line = postimage.line_allocated;
+
for (;;) {
applied_pos = find_pos(img, &preimage, &postimage,
--
1.5.4.2.g41ac4
next prev parent reply other threads:[~2008-02-02 10:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 10:54 [PATCH/RFC 00/13] git-apply --whitespace=fix updates Junio C Hamano
2008-02-02 10:54 ` [PATCH 01/13] builtin-apply.c: refactor small part that matches context Junio C Hamano
2008-02-02 10:54 ` [PATCH 02/13] builtin-apply.c: restructure "offset" matching Junio C Hamano
2008-02-02 10:54 ` [PATCH 03/13] builtin-apply.c: push match-beginning/end logic down Junio C Hamano
2008-02-02 10:54 ` [PATCH 04/13] builtin-apply.c: make it more line oriented Junio C Hamano
2008-02-02 10:54 ` [PATCH 05/13] builtin-apply.c: optimize match_beginning/end processing a bit Junio C Hamano
2008-02-02 10:54 ` Junio C Hamano [this message]
2008-02-02 10:54 ` [PATCH 07/13] builtin-apply.c: clean-up apply_one_fragment() Junio C Hamano
2008-02-02 10:54 ` [PATCH 08/13] builtin-apply.c: simplify calling site to apply_line() Junio C Hamano
2008-02-02 10:54 ` [PATCH 09/13] builtin-apply.c: do not feed copy_wsfix() leading '+' Junio C Hamano
2008-02-02 10:54 ` [PATCH 10/13] builtin-apply.c: move copy_wsfix() function a bit higher Junio C Hamano
2008-02-02 10:54 ` [PATCH 11/13] builtin-apply.c: pass ws_rule down to match_fragment() Junio C Hamano
2008-02-02 10:54 ` [PATCH 12/13] git-apply --whitespace=fix: fix whitespace fuzz introduced by previous run Junio C Hamano
2008-02-02 10:54 ` [PATCH 13/13] core.whitespace: cr-at-eol Junio C Hamano
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=1201949659-27725-7-git-send-email-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/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).