From: Thomas Rast <trast@student.ethz.ch>
To: Junio C Hamano <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Subject: Re: Branch shuffling after 1.6.6 release plans
Date: Fri, 25 Dec 2009 12:30:34 +0100 [thread overview]
Message-ID: <200912251230.48243.trast@student.ethz.ch> (raw)
In-Reply-To: <7vljgrgar9.fsf@alter.siamese.dyndns.org>
Thanks for 1.6.6!
Junio C Hamano wrote:
> * tr/maint-merge-ours-clarification (2009-11-15) 1 commit
> - rebase: refuse to rebase with -s ours
>
> I do not think we reached a concensus for solving conflicts between "give
> them rope" and "protect users from clearly meaningless combinations". The
> author obviously is for the latter (and I am inclined to agree); Dscho
> seems to think otherwise.
I can try hacking some internal option into the merge helpers, by
which they declare to be (in)compatible with rebasing. I think this
what Dscho or Sverre mentioned in the corresponding thread, but I
forgot about it when I noticed you had already promoted the above to
'next'.
> * tr/reset-checkout-patch (2009-11-19) 1 commit
> - {checkout,reset} -p: make patch direction configurable
>
> I do not particularly like a configuration like this that changes the
> behaviour of a command in a drastic way---it will make helping others
> much harder.
I think it's not quite as drastic as you make it sound ;-)
But I don't need this feature, and Peff mentioned something about
being happy except for the patch editing mode. Unfortunately the
above pretty much hits the limits of add--interactive's flexibility,
so an interactive direction toggling feature would need some rewiring.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2009-12-25 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 1:06 [ANNOUNCE] Git 1.6.6 Junio C Hamano
2009-12-24 18:01 ` Some stats for 1.6.6 Junio C Hamano
2009-12-24 19:43 ` Shawn O. Pearce
2009-12-25 0:25 ` Branch shuffling after 1.6.6 release plans Junio C Hamano
2009-12-25 11:30 ` Thomas Rast [this message]
2009-12-25 12:28 ` Ilari Liusvaara
2009-12-26 8:01 ` Jeff King
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=200912251230.48243.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.