All of lore.kernel.org
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: git@vger.kernel.org
Subject: suggestions for generating diffs through the revision list
Date: Tue, 17 Jun 2008 17:41:42 -0400	[thread overview]
Message-ID: <20080617214142.GM16941@redhat.com> (raw)

I am try to walk the revision history for a given path and analyze the
diff (as compared to its parent).  What is the proper way of doing that?

I noticed a bunch of 'library' calls such as

init_revsion(&revs);
setup_revisions(argc, argv, &revs, "HEAD");
prepare_revision_walk(&revs, NULL);
commit = get_revision(&revs);

But what I can't find is the way to generate diffs.  I see lots and lots
of code to do it, but every builtin seems to do it differently.  Not
knowing the internals that well, I was hoping for some advice.

I stumbled upon calls like

run_diff_files
run_diff_index

but I haven't seen how to use them correctly.

Any help would be appreciated.  Thanks.

Cheers,
Don

             reply	other threads:[~2008-06-17 21:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-17 21:41 Don Zickus [this message]
2008-06-17 22:04 ` suggestions for generating diffs through the revision list Junio C Hamano
2008-06-19 21:20   ` Don Zickus

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=20080617214142.GM16941@redhat.com \
    --to=dzickus@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.