From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Diff format in packs
Date: Mon, 31 Jul 2006 23:16:19 +0200 [thread overview]
Message-ID: <ealruh$sq9$1@sea.gmane.org> (raw)
In-Reply-To: 9e4733910607311408i10e17dse776920de7c5076a@mail.gmail.com
Jon Smirl wrote:
> I'm trying to build a small app that takes a CVS ,v and writes out a
> pack corresponding to the versions. Suggestions on the most efficient
> strategy for doing this by calling straight into the git C code?
> Forking off git commands is not very efficient when done a million
> times.
Something akin to parsecvs by Keith Packard?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-07-31 21:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 21:08 Diff format in packs Jon Smirl
2006-07-31 21:16 ` Jakub Narebski [this message]
2006-07-31 21:20 ` Jon Smirl
2006-07-31 22:32 ` Shawn Pearce
2006-07-31 23:08 ` Jon Smirl
2006-08-01 0:47 ` Martin Langhoff
2006-08-01 1:03 ` Martin Langhoff
2006-08-01 1:13 ` Jon Smirl
2006-08-01 2:16 ` Martin Langhoff
2006-08-01 2:29 ` Jon Smirl
2006-08-01 2:36 ` Martin Langhoff
2006-08-01 10:59 ` Johannes Schindelin
2006-08-01 12:01 ` Jakub Narebski
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='ealruh$sq9$1@sea.gmane.org' \
--to=jnareb@gmail.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).