From: Sitaram Chamarty <sitaramc@gmail.com>
To: git@vger.kernel.org
Subject: thoughts on a possible "pre-upload" hook
Date: Tue, 22 Sep 2009 15:50:09 +0530 [thread overview]
Message-ID: <2e24e5b90909220320rbd5fd1l40c7898656445232@mail.gmail.com> (raw)
Hello,
As git is used more and more in corporate-type environments, at some
point it becomes convenient to have *branches* (or more accurately,
refs) that are not readable. The simplest way to do this (from git's
point of view) is to allow a "pre-upload" hook, rather like the
"pre-receive" hook or "update" hook.
I don't know the upload pack protocol enough to know whether this is a
stupid idea or not; please tell me if so :-) But things that were
seemingly "impossible" in the early days are being talked about now
and even being implemented so I felt brave enough to ask.
I'm afraid my C programming days are long gone, but if anything can be
done in shell or perl, with a little git.guidance, I'll do whatever I
can.
--
Sitaram
next reply other threads:[~2009-09-22 10:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 10:20 Sitaram Chamarty [this message]
2009-09-22 16:00 ` thoughts on a possible "pre-upload" hook Randal L. Schwartz
2009-09-22 16:05 ` Matthieu Moy
2009-09-22 16:17 ` Shawn O. Pearce
2009-09-25 11:54 ` Sitaram Chamarty
2009-09-25 12:29 ` Matthieu Moy
2009-09-25 13:43 ` Sitaram Chamarty
2009-09-28 2:01 ` Adam Brewster
2009-09-28 3:02 ` Sitaram Chamarty
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=2e24e5b90909220320rbd5fd1l40c7898656445232@mail.gmail.com \
--to=sitaramc@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).