From: Shawn Pearce <spearce@spearce.org>
To: madmarcos <fru574@my.utsa.edu>
Cc: git@vger.kernel.org
Subject: Re: capturing the packfile from git-upload-pack
Date: Fri, 15 Apr 2011 11:46:44 -0400 [thread overview]
Message-ID: <BANLkTimAt_gcp1uBR_0H7LJHUdFGqHbRvA@mail.gmail.com> (raw)
In-Reply-To: <1302837720729-6275146.post@n2.nabble.com>
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. :-)
--
Shawn.
next prev parent reply other threads:[~2011-04-15 15:47 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 [this message]
2011-04-15 17:46 ` Junio C Hamano
2011-04-15 19:09 ` Jeff King
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=BANLkTimAt_gcp1uBR_0H7LJHUdFGqHbRvA@mail.gmail.com \
--to=spearce@spearce.org \
--cc=fru574@my.utsa.edu \
--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).