From: john at keeping.me.uk (John Keeping)
Subject: [PATCH 1/3] parsing.c: make commit buffer const
Date: Sun, 27 Jul 2014 11:56:18 +0100 [thread overview]
Message-ID: <4264f0f44cb0d11a790d93e91226f539ec03b9c1.1406458339.git.john@keeping.me.uk> (raw)
In-Reply-To: <cover.1406458339.git.john@keeping.me.uk>
This will be required in order to incorporate the changes to commit
buffer handling in Git 2.0.2.
Signed-off-by: John Keeping <john at keeping.me.uk>
---
parsing.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/parsing.c b/parsing.c
index 073f46f..edb3416 100644
--- a/parsing.c
+++ b/parsing.c
@@ -69,9 +69,9 @@ static char *substr(const char *head, const char *tail)
return buf;
}
-static char *parse_user(char *t, char **name, char **email, unsigned long *date)
+static const char *parse_user(const char *t, char **name, char **email, unsigned long *date)
{
- char *p = t;
+ const char *p = t;
int mode = 1;
while (p && *p) {
@@ -132,7 +132,7 @@ static const char *reencode(char **txt, const char *src_enc, const char *dst_enc
struct commitinfo *cgit_parse_commit(struct commit *commit)
{
struct commitinfo *ret;
- char *p = commit->buffer, *t;
+ const char *p = commit->buffer, *t;
ret = xmalloc(sizeof(*ret));
ret->commit = commit;
@@ -223,7 +223,7 @@ struct taginfo *cgit_parse_tag(struct tag *tag)
void *data;
enum object_type type;
unsigned long size;
- char *p;
+ const char *p;
struct taginfo *ret;
data = read_sha1_file(tag->object.sha1, &type, &size);
--
2.0.1.472.g6f92e5f.dirty
next prev parent reply other threads:[~2014-07-27 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-27 10:56 [PATCH 0/3] Update to Git 2.0.3 john
2014-07-27 10:56 ` john [this message]
2014-07-27 10:56 ` [PATCH 2/3] git: update to v2.0.3 john
2014-07-27 10:56 ` [PATCH 3/3] ui-stats.c: set parent pointer to NULL after freeing it john
2014-07-27 23:59 ` [PATCH 0/3] Update to Git 2.0.3 Jason
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=4264f0f44cb0d11a790d93e91226f539ec03b9c1.1406458339.git.john@keeping.me.uk \
--to=cgit@lists.zx2c4.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).