From: Sitaram Chamarty <sitaramc@gmail.com>
To: Adam Brewster <adambrewster@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: thoughts on a possible "pre-upload" hook
Date: Mon, 28 Sep 2009 08:32:17 +0530 [thread overview]
Message-ID: <2e24e5b90909272002r53b0a82dw9cb52bdc7bbd477@mail.gmail.com> (raw)
In-Reply-To: <c376da900909271901q1667ecacw730ba5180a558f3b@mail.gmail.com>
On Mon, Sep 28, 2009 at 7:31 AM, Adam Brewster <adambrewster@gmail.com> wrote:
>> 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.
>>
>
> What's the benefit of this over using multiple repositories?
Over a long pm chat over irc with Ilari, I have come to the same
conclusion. I was hoping there would be some administrative
convenience or workflow convenience to doing this, but whether there
is or not is debatable, and even if there is, there are enough failure
modes to make this have a lot of caveats.
--
Sitaram
prev parent reply other threads:[~2009-09-28 3:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 10:20 thoughts on a possible "pre-upload" hook Sitaram Chamarty
2009-09-22 16:00 ` 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 [this message]
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=2e24e5b90909272002r53b0a82dw9cb52bdc7bbd477@mail.gmail.com \
--to=sitaramc@gmail.com \
--cc=adambrewster@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).