From: Pavel Roskin <proski@gnu.org>
To: git <git@vger.kernel.org>
Subject: Locking a branch
Date: Sat, 06 May 2006 22:50:43 -0400 [thread overview]
Message-ID: <1146970243.24434.77.camel@dv> (raw)
Hello!
I see there is an active discussion about branch attributes. It would
be nice to have an attribute to prevent git from changing the branch
head in any way. The reason is that it interferes with StGIT on StGIT
managed branches. If StGIT is fine with the change, it would remove or
override the lock temporarily. StGIT could also unlock the branch
permanently if there are no applied patches.
Another use of the branch lock would be to prevent damage to remote
branches, such as "origin". Committing anything to "origin" would break
fetching. In this case, git-fetch should be allowed to override the
lock after checking .git/remotes, but other git commands should respect
the lock.
It should be possible to break locks, but the users would at least think
before doing so.
--
Regards,
Pavel Roskin
next reply other threads:[~2006-05-07 2:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-07 2:50 Pavel Roskin [this message]
2006-05-08 10:45 ` Locking a branch Catalin Marinas
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=1146970243.24434.77.camel@dv \
--to=proski@gnu.org \
--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).