git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: madmarcos <fru574@my.utsa.edu>,
	Shawn Pearce <spearce@spearce.org>,
	git@vger.kernel.org
Subject: Re: capturing the packfile from git-upload-pack
Date: Fri, 15 Apr 2011 15:09:08 -0400	[thread overview]
Message-ID: <20110415190908.GA4093@sigill.intra.peff.net> (raw)
In-Reply-To: <7vy63bcsqz.fsf@alter.siamese.dyndns.org>

On Fri, Apr 15, 2011 at 10:46:28AM -0700, Junio C Hamano wrote:

> Shawn Pearce <spearce@spearce.org> writes:
> 
> > On Thu, Apr 14, 2011 at 23:22, madmarcos <fru574@my.utsa.edu> wrote:
> >> is there a git command that can capture in a separate file the packfile that
> >> is generated and transmitted from a "want"ed branch during the
> >> git-upload-pack command? I need a good sample to study.
> >
> > No.
> >
> > But you can create an input file yourself, the pkt-line format is
> > pretty simple. Pipe the input to git-upload-pack, and it will spit
> > back the response. :-)
> 
> If you are running 1.7.5-rc0 or newer, GIT_TRACE_PACKET may also be of
> help.

Sadly, no. I punted on outputting the actual pack since it is big and
binary, and I was only interested in the ref negotiation. My eventual
plan was that you could do:

  GIT_TRACE_PACKET=2 GIT_TRACE_PACKET_PACK=/tmp/foo.pack \
    git clone ...

and get the ref negotiation on stderr, and the pack dumped in a file.
However, there is one stumbling block: the packet tracing happens at a
very low level, and doesn't know if we are doing sideband-demuxing or
not. And it would need to know to that to put the proper data in the
packfile.

It may just be a matter of implementing the packfile tracing at a
slightly different layer (where we have already demuxed), but I haven't
looked closely at it.

-Peff

  reply	other threads:[~2011-04-15 19:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15  3:22 capturing the packfile from git-upload-pack madmarcos
2011-04-15 15:46 ` Shawn Pearce
2011-04-15 17:46   ` Junio C Hamano
2011-04-15 19:09     ` Jeff King [this message]
2011-04-15 19:25       ` Jeff King
2011-04-16  0:59   ` madmarcos

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=20110415190908.GA4093@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=fru574@my.utsa.edu \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=spearce@spearce.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).