From: "J. Bruce Fields" <bfields@fieldses.org>
To: kurt_p_lloyd <kplloyd@alcatel-lucent.com>
Cc: git@vger.kernel.org, Keith Duthie <keith@no.net.nz>,
Junio C Hamano <gitster@pobox.com>,
Kevin Green <Kevin.T.Green@morganstanley.com>
Subject: Re: pull/merge --no-commit
Date: Thu, 7 Jun 2007 16:43:33 -0400 [thread overview]
Message-ID: <20070607204333.GC14463@fieldses.org> (raw)
In-Reply-To: <46686B63.6080808@alcatel-lucent.com>
On Thu, Jun 07, 2007 at 04:32:35PM -0400, kurt_p_lloyd wrote:
> One thing I was thinking might be useful would be a command to make
> (just) my repository unavailable for 'fetch' or 'pull' from others,
> temporarily. And then a command to make it available again,
> after I finish things that could end up needing "database" surgery,
> like maybe something that could result in having to do a git reset.
> I was thinking maybe something like:
>
> $ git config maintenance true
> .... do something that may end up needing "database" surgery
> $ git config maintenance false
You could probably do that with file permissions, but...
> Just an idea. Of course, if something like this already exists ....
> (I'd rather not shut down sshd, nor have to create a separate "public"
> repository (for certain types of "projects" anyway).)
... why not? Having a separate public repository also allows you to do
this and much more. And it should be cheap and easy--if you're worried
about the space, clone with --shared or something.
--b.
next prev parent reply other threads:[~2007-06-07 20:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 4:26 pull/merge --no-commit kurt_p_lloyd
2007-06-07 4:39 ` kurt_p_lloyd
2007-06-07 5:24 ` Junio C Hamano
2007-06-07 18:31 ` kurt_p_lloyd
2007-06-07 18:58 ` Junio C Hamano
2007-06-07 18:59 ` Kevin Green
2007-06-07 19:12 ` Keith Duthie
2007-06-07 20:32 ` kurt_p_lloyd
2007-06-07 20:43 ` J. Bruce Fields [this message]
2007-06-07 20:51 ` Keith Duthie
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=20070607204333.GC14463@fieldses.org \
--to=bfields@fieldses.org \
--cc=Kevin.T.Green@morganstanley.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=keith@no.net.nz \
--cc=kplloyd@alcatel-lucent.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.