From: Erick Mattos <erick.mattos@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] git checkout -b: unparent the new branch with -o
Date: Tue, 16 Mar 2010 15:18:02 -0300 [thread overview]
Message-ID: <55bacdd31003161118m59bc6066id2aaf7b165a601a6@mail.gmail.com> (raw)
In-Reply-To: <7vmxyajns5.fsf@alter.siamese.dyndns.org>
2010/3/14 Junio C Hamano <gitster@pobox.com>:
> Erick Mattos <erick.mattos@gmail.com> writes:
>
>> As I see you have found a very good example under your common work
>> flow. Nice. :-)
>
> And realize that it does not help that you nuke the index while leaving
> the working tree files.
>
> I do not think you got my point at all, so let's try a different phrasing.
> I've already spent too much time on this thread, so this will be the last
> message from me on this topic for now. Hopefully you will understand this
> time.
>
> I saw two potential workflows that could be useful:
It is an evolution we are not talking about its usefulness anymore.
However it is not a matter of understanding too. :-) It is about opinion.
It is just that you do not like the actual behavior and I do.
But you rule and this is just a detail anyway so I will be sending a
new version in a few moments.
Regards
next prev parent reply other threads:[~2010-03-16 18:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 22:28 [PATCH v2] git checkout -b: unparent the new branch with -o Erick Mattos
2010-03-12 6:53 ` Junio C Hamano
2010-03-12 7:40 ` Bert Wesarg
2010-04-27 6:35 ` David Kågedal
2010-03-12 16:45 ` Erick Mattos
2010-03-13 7:53 ` Junio C Hamano
2010-03-13 9:10 ` Junio C Hamano
2010-03-14 21:57 ` Erick Mattos
2010-03-15 2:56 ` Junio C Hamano
2010-03-16 18:18 ` Erick Mattos [this message]
2010-03-13 9:33 ` Jakub Narebski
2010-03-13 9:42 ` Junio C Hamano
2010-03-14 21:57 ` Erick Mattos
2010-03-15 2:06 ` Junio C Hamano
2010-03-16 18:17 ` Erick Mattos
2010-03-14 20:46 ` Erick Mattos
2010-03-14 21:58 ` Erick Mattos
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=55bacdd31003161118m59bc6066id2aaf7b165a601a6@mail.gmail.com \
--to=erick.mattos@gmail.com \
--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 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).