git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mahesh Vaidya <forvaidya@gmail.com>
To: git@vger.kernel.org
Subject: How does receive-pack and pre-receive hook works ?
Date: Sun, 27 Jun 2010 07:54:51 +0530	[thread overview]
Message-ID: <AANLkTinYRF2m95MU2c817bK6mfehPt_OMBH45R6laNUe@mail.gmail.com> (raw)

How does receive-pack and pre-receive hook works ?

I have added following in pre-recieve hook; all works fine. git
rev-list --pretty d6d147f432869037a7ac8bdca3a2d5bc0cdc1e9f
^a3fe19833480023b72350d6e56e939cbd0ba2c8b

I Would like know where does Git saves whatever I am pushing before
exit 0 of this hook; Specifically how does it understand about
'd6d147f432869037a7ac8bdca3a2d5bc0cdc1e9f' which is not part of
destination depot / repo.

Thx/ Mahesh.

             reply	other threads:[~2010-06-27  2:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-27  2:24 Mahesh Vaidya [this message]
2010-06-27  7:00 ` How does receive-pack and pre-receive hook works ? Shawn Pearce

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=AANLkTinYRF2m95MU2c817bK6mfehPt_OMBH45R6laNUe@mail.gmail.com \
    --to=forvaidya@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).