From: "Jean-Noël Avila" <avila.jn@gmail.com>
To: git <git@vger.kernel.org>
Subject: Tagging a branch as "not fitted for branching" ?
Date: Mon, 28 Apr 2014 14:09:43 +0200 [thread overview]
Message-ID: <535E4507.2070805@gmail.com> (raw)
Most manuals on git state that it is bad practice to push -f a branch
after have meddled with its history, because this would risk to upset
the repositories of the coworkers. On the other hand, some workflows use
branches to propose modifications, and need some rewritting of the
history after some review steps. In this case, the branch should only be
seen as a mere pile of patches. Having this two-sided discourse is often
misunderstood by casual git users.
The proposed solution would be to be able to flag the branches with a
special tag "not fitted for branching" that a collaborator could use
when pushing it. This tag would be passed on to any pulled remote. When
another collaborator would then issue a "git checkout -b", the command
would fail with a warning message, unless forced with '-f'.
Is this feature already present? If not, would it be of any interest?
Best regards,
Jean-Noël AVILA
next reply other threads:[~2014-04-28 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 12:09 Jean-Noël Avila [this message]
2014-04-28 23:34 ` Tagging a branch as "not fitted for branching" ? Junio C Hamano
2014-04-29 7:37 ` Jean-Noël Avila
2014-04-29 17:43 ` Junio C Hamano
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=535E4507.2070805@gmail.com \
--to=avila.jn@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).