From: Theodore Ts'o <tytso@mit.edu>
To: Junio C Hamano <gitster@pobox.com>
Cc: Josef 'Jeff' Sipek <jeffpc@josefsipek.net>,
Per Cederqvist <ceder@lysator.liu.se>,
git@vger.kernel.org
Subject: Re: [PATCH] Added guilt.reusebranch configuration option.
Date: Wed, 22 May 2013 14:04:03 -0400 [thread overview]
Message-ID: <20130522180403.GB20848@thunk.org> (raw)
In-Reply-To: <7v8v36kiau.fsf@alter.siamese.dyndns.org>
On Wed, May 22, 2013 at 10:58:49AM -0700, Junio C Hamano wrote:
> Theodore Ts'o <tytso@mit.edu> writes:
>
> > I was actually thinking that it might be interesting to have a
> > branch.<branch>.rewindable, which would change the guilt defaults, and
> > could also key changes in key git behavior which makes it less likely
> > that a user shoots him or herself in the foot --- i.e., give warnings
> > if he or she has modified the branch in such a way that
> > remotes.origin.<branch> is no longer contained within the branch head.
>
> At least "rebase" can pay attention to it and might make the world a
> better place.
Yeah, rebase was the primary command I was thinking about. The other
one would be "git commit --amend" after the branch had been pushed
out.
- Ted
next prev parent reply other threads:[~2013-05-22 18:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 2:55 [PATCH] guilt: force the use of bare branches Theodore Ts'o
2013-05-22 3:29 ` Josef 'Jeff' Sipek
2013-05-22 12:11 ` [PATCH -v2] " Theodore Ts'o
2013-05-22 12:39 ` Per Cederqvist
2013-05-22 13:01 ` [PATCH] Added guilt.reusebranch configuration option Per Cederqvist
2013-05-22 13:42 ` Josef 'Jeff' Sipek
2013-05-22 14:45 ` Theodore Ts'o
2013-05-22 16:31 ` Josef 'Jeff' Sipek
2013-05-22 17:58 ` Junio C Hamano
2013-05-22 18:04 ` Theodore Ts'o [this message]
2013-05-22 18:55 ` Junio C Hamano
2013-05-23 2:11 ` Theodore Ts'o
2013-05-23 9:52 ` Ramkumar Ramachandra
2013-05-23 18:37 ` Theodore Ts'o
2013-05-23 19:06 ` Ramkumar Ramachandra
2013-05-23 19:14 ` Junio C Hamano
2013-05-23 19:01 ` 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=20130522180403.GB20848@thunk.org \
--to=tytso@mit.edu \
--cc=ceder@lysator.liu.se \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jeffpc@josefsipek.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).