From: Yaroslav Halchenko <yoh@onerussian.com>
To: Git Gurus hangout <git@vger.kernel.org>
Cc: Benjamin Poldrack <benjaminpoldrack@gmail.com>,
Joey Hess <id@joeyh.name>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: 'next'ed --allow-unrelated-histories could cause lots of grief
Date: Thu, 21 Apr 2016 16:36:06 -0400 [thread overview]
Message-ID: <20160421203606.GM23764@onerussian.com> (raw)
In-Reply-To: <xmqqinzasqgv.fsf@gitster.mtv.corp.google.com>
On Thu, 21 Apr 2016, Junio C Hamano wrote:
> >> It is not very productive to make such an emotional statement
> >> without substantiating _why_ a merge that adds a new root, which was
> >> declared in the thread above as "crap" (in the context of the kernel
> >> project),
> > Sorry if my statement sounded too emotional ;) I will outline some of
> > the use-cases below.
> Thanks. Emotional is fine, as long as you _also_ have useful
> information.
Gotcha: I will follow "emotional + useful == fine" advice closer
next time ;)
Thank you a lot for the suggested patch with the env variable
workaround!
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
next prev parent reply other threads:[~2016-04-21 20:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 16:10 'next'ed --allow-unrelated-histories could cause lots of grief Yaroslav Halchenko
2016-04-21 16:41 ` Junio C Hamano
2016-04-21 18:55 ` Yaroslav Halchenko
2016-04-21 19:37 ` Junio C Hamano
2016-04-21 20:36 ` Yaroslav Halchenko [this message]
2016-04-21 22:57 ` Joey Hess
2016-04-21 23:17 ` Junio C Hamano
2016-04-21 18:19 ` Joey Hess
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=20160421203606.GM23764@onerussian.com \
--to=yoh@onerussian.com \
--cc=benjaminpoldrack@gmail.com \
--cc=git@vger.kernel.org \
--cc=id@joeyh.name \
--cc=torvalds@linux-foundation.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 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.