From: Linus Torvalds <torvalds@osdl.org>
To: Junio C Hamano <junkio@cox.net>, Git Mailing List <git@vger.kernel.org>
Subject: [PATCH 0/3] git-rev-list libification effort: the next stage
Date: Tue, 28 Feb 2006 11:19:41 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0602281115110.22647@g5.osdl.org> (raw)
Ok, the following three patches that I'll send out are still pretty rough,
but they actually get us to the first real point of this whole exercise:
writing one of the trivial git helper scripts in C.
In particular, at the end, we have "git log" being implemented as this
trivial C function:
#define LOGSIZE (65536)
static int cmd_log(int argc, char **argv, char **envp)
{
struct rev_info rev;
struct commit *commit;
char *buf = xmalloc(LOGSIZE);
argc = setup_revisions(argc, argv, &rev, "HEAD");
prepare_revision_walk(&rev);
setup_pager();
while ((commit = get_revision(&rev)) != NULL) {
pretty_print_commit(CMIT_FMT_DEFAULT, commit, ~0, buf, LOGSIZE, 18);
printf("%s\n", buf);
}
free(buf);
return 0;
}
which is actually a pretty good example of what I wanted to do. It's
not perfect yet (it doesn't parse the "--pretty=xxx" option yet, nor the
"--since" and "--until" dates, for example), but I think this is all
going in the right direction.
Linus
next reply other threads:[~2006-02-28 19:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 19:19 Linus Torvalds [this message]
2006-02-28 19:24 ` [PATCH 1/3] git-rev-list libification: rev-list walking Linus Torvalds
2006-02-28 19:26 ` [PATCH 2/3] Introduce trivial new pager.c helper infrastructure Linus Torvalds
2006-02-28 19:30 ` [PATCH 3/3] Tie it all together: "git log" Linus Torvalds
2006-02-28 20:59 ` Linus Torvalds
2006-02-28 22:22 ` Junio C Hamano
2006-02-28 23:07 ` Linus Torvalds
2006-03-01 12:24 ` [PATCH 1/2] git-log (internal): add approxidate Junio C Hamano
2006-03-01 12:24 ` [PATCH 2/2] git-log (internal): more options Junio C Hamano
2006-03-01 15:43 ` Linus Torvalds
2006-03-01 20:06 ` Junio C Hamano
2006-02-28 23:38 ` [PATCH 3/3] Tie it all together: "git log" Martin Langhoff
2006-03-01 9:02 ` 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=Pine.LNX.4.64.0602281115110.22647@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).