git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Glanzmann <thomas@glanzmann.de>
To: Jeff King <peff@peff.net>
Cc: GIT <git@vger.kernel.org>
Subject: Re: Update a bare repository
Date: Tue, 17 Jul 2007 09:26:35 +0200	[thread overview]
Message-ID: <20070717072635.GG5823@cip.informatik.uni-erlangen.de> (raw)
In-Reply-To: <20070717070428.GA13266@coredump.intra.peff.net>

Hello,

> The "+" in both cases means that it copies whatever Junio has, even if
> it might lose some commits of yours. But that seems to be what you
> want in this case.

thanks a lot. That is exactly what I was looking for.

> The simplest thing is not to give write access to the repo for your
> pushers. However, you could also put in a pre-receive hook that rejects
> all pushes.

Is there an example somewhere?

	Thomas

  reply	other threads:[~2007-07-17  7:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17  6:30 Update a bare repository Thomas Glanzmann
2007-07-17  7:04 ` Jeff King
2007-07-17  7:26   ` Thomas Glanzmann [this message]
2007-07-17  7:31     ` Jeff King
2007-07-17  7:41       ` Thomas Glanzmann

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=20070717072635.GG5823@cip.informatik.uni-erlangen.de \
    --to=thomas@glanzmann.de \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).