From: Arun Raghavan <ford_prefect@gentoo.org>
To: "Robin H. Johnson" <robbat2@gentoo.org>
Cc: gentoo-scm@lists.gentoo.org
Subject: [gentoo-scm] New hooks for git, was: Progress summary, 2009/06/01
Date: Wed, 10 Jun 2009 01:12:47 +0530 [thread overview]
Message-ID: <1244576567.11371.11.camel@peripatetic.hades> (raw)
In-Reply-To: <20090601234549.GA3042@orbis-terrarum.net>
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
On Mon, 2009-06-01 at 16:45 -0700, Robin H. Johnson wrote:
> - Finish new hooks for git:
> upload-pack.c - get_common_commits:
> right before the 'return 0', check for and launch a new hook,
> passing
> the have/want headers via stdin, and use the return code (AND the
> stderr) to see if we should halt.
Could you expand on this? Doesn't sound too complex - if I understand
this, 'have' is the set of heads of branches that the server has and
'want' is the set of branches that the client figures it needs to update
(simplifying a little from [1]).
That said, when do we want to terminate the upload?
Best,
Arun
[1] http://git-scm.com/gitserver.txt
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-06-09 19:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 23:45 [gentoo-scm] Progress summary, 2009/06/01 Robin H. Johnson
2009-06-05 12:59 ` [gentoo-scm] gpg signing of commits, was: " Robert Buchholz
2009-06-05 18:54 ` Robin H. Johnson
2009-06-09 1:50 ` Robert Buchholz
2009-06-09 2:46 ` Robin H. Johnson
2009-06-07 22:18 ` [gentoo-scm] " Donnie Berkholz
2009-06-07 22:27 ` Nirbheek Chauhan
2009-06-09 19:42 ` Arun Raghavan [this message]
2009-06-09 20:16 ` [gentoo-scm] New hooks for git, was: " Robin H. Johnson
2009-08-27 22:59 ` [gentoo-scm] Progress summary, 2009/08/27 Robin H. Johnson
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=1244576567.11371.11.camel@peripatetic.hades \
--to=ford_prefect@gentoo.org \
--cc=gentoo-scm@lists.gentoo.org \
--cc=robbat2@gentoo.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