From: Brendan Miller <catphive@catphive.net>
To: git@vger.kernel.org
Subject: preventing destructive operations to central repository
Date: Thu, 15 Apr 2010 17:39:42 -0700 [thread overview]
Message-ID: <j2yef38762f1004151739x497106eeo190b97f3eecc153f@mail.gmail.com> (raw)
Let's say you have a bare git repository writeable by a number of
different people. How do you prevent them from borking the central
repository?
Also, is there an automated mechanism to ensure that the timeline
stays clean? Say, force people to rebase their repositories before
merging into the shared repository?
Thanks
next reply other threads:[~2010-04-16 0:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 0:39 Brendan Miller [this message]
2010-04-16 0:58 ` preventing destructive operations to central repository Jay Soffian
2010-04-16 1:03 ` Shawn O. 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=j2yef38762f1004151739x497106eeo190b97f3eecc153f@mail.gmail.com \
--to=catphive@catphive.net \
--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).