From: Mark Levedahl <mdl123@verizon•net>
To: Junio C Hamano <junkio@cox•net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx•de>, git@vger•kernel.org
Subject: Re: [PATCH] Add git-bundle: move objects and references by archive
Date: Thu, 22 Feb 2007 21:32:57 -0500 [thread overview]
Message-ID: <45DE5259.6090502@verizon.net> (raw)
In-Reply-To: <7v8xeqllxk.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
>> diff --git a/Documentation/cmd-list.perl b/Documentation/cmd-list.perl
>> index a2d6268..f61c77a 100755
>> --- a/Documentation/cmd-list.perl
>> +++ b/Documentation/cmd-list.perl
>> @@ -70,6 +70,7 @@ git-archive mainporcelain
>> git-bisect mainporcelain
>> git-blame ancillaryinterrogators
>> git-branch mainporcelain
>> +git-bundle mainporcelain
>> git-cat-file plumbinginterrogators
>> git-checkout-index plumbingmanipulators
>> git-checkout mainporcelain
>>
>
> Is this really a mainporcelain?
> I would say ancillarymanipulators (or perhaps synchelpers).
>
>
git bundle has four commands: create, verify, list-heads, and unbundle.
The last two are pure helper functions, basically plumbing. Verify is
questionable as to where it lies. But, create is the only way to create
a bundle, is logically equivalent to git push as a user command to move
data, so I called it mainporcelain because that is how git push is
classified.
>> + /* write prerequisites */
>> + memcpy(argv_boundary + 2, argv + 1, argc * sizeof(const char *));
>> + argv_boundary[0] = "rev-list";
>> + argv_boundary[1] = "--boundary";
>> + argv_boundary[argc + 1] = NULL;
>> + out = -1;
>> + pid = fork_with_pipe(argv_boundary, NULL, &out);
>> + if (pid < 0)
>> + return -1;
>> + while ((i = read_string(out, buffer, sizeof(buffer))) > 0)
>> + if (buffer[0] == '-')
>> + write(bundle_fd, buffer, i);
>>
>
> It would be helpful for the recipient if you can append output
> from git-describe (or name-rev) when the buffer lacks "name".
>
I found the actual commit summary message (i.e., git-rev-list
--pretty=one --max-count=1 sha1) the most useful of the various
summaries available.
Mark
next prev parent reply other threads:[~2007-02-23 2:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.63.0702220157130.22628@wbgn013.biozentrum.uni-wuerz burg.de>
2007-02-22 0:59 ` [PATCH] Add git-bundle: move objects and references by archive Johannes Schindelin
2007-02-22 3:28 ` Nicolas Pitre
2007-02-22 15:55 ` Johannes Schindelin
2007-02-22 16:14 ` Simon 'corecode' Schubert
2007-02-22 16:28 ` Nicolas Pitre
2007-02-22 16:37 ` Johannes Schindelin
2007-02-22 16:46 ` Simon 'corecode' Schubert
2007-02-22 17:09 ` Johannes Schindelin
2007-02-22 16:24 ` Nicolas Pitre
2007-02-22 17:12 ` Johannes Schindelin
2007-02-22 17:21 ` Nicolas Pitre
2007-02-22 6:56 ` Junio C Hamano
2007-02-22 7:08 ` Junio C Hamano
2007-02-22 16:20 ` Johannes Schindelin
2007-02-22 19:10 ` Junio C Hamano
2007-02-22 19:16 ` Johannes Schindelin
2007-02-22 20:05 ` Junio C Hamano
2007-02-22 20:25 ` Johannes Schindelin
2007-02-22 16:17 ` Johannes Schindelin
2007-02-23 2:32 ` Mark Levedahl [this message]
2007-02-23 4:39 ` Junio C Hamano
2007-02-22 9:31 ` Johannes Sixt
2007-02-22 18:14 ` [PATCH] git-bundle: assorted fixes Johannes Schindelin
2007-02-23 1:36 ` Mark Levedahl
2007-02-23 1:56 ` Johannes Schindelin
2007-02-23 2:12 ` Mark Levedahl
2007-02-23 2:17 ` Johannes Schindelin
2007-02-23 3:37 ` Mark Levedahl
2007-02-18 22:47 [PATCH] Add git-bundle: move objects and references by archive Mark Levedahl
2007-02-19 1:07 ` Johannes Schindelin
2007-02-19 1:50 ` Junio C Hamano
2007-02-19 2:02 ` Johannes Schindelin
2007-02-19 7:56 ` Shawn O. Pearce
2007-02-19 13:29 ` Mark Levedahl
2007-02-19 15:03 ` Johannes Schindelin
2007-02-19 1:49 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2007-02-17 18:41 [PATCH] Add git-unbundle - unpack objects and references for disconnected transfer Junio C Hamano
2007-02-18 17:27 ` [PATCH] Add git-bundle: move objects and references by archive Mark Levedahl
2007-02-18 22:47 ` Mark Levedahl
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=45DE5259.6090502@verizon.net \
--to=mdl123@verizon$(echo .)net \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=junkio@cox$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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