From: Linus Torvalds <torvalds@osdl.org>
To: Andreas Ericsson <ae@op5.se>
Cc: Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org, Anton Altaparmakov <aia21@cam.ac.uk>
Subject: Re: Best way to generate a git tree containing only a subset of commits from another tree?
Date: Wed, 22 Mar 2006 19:43:25 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0603221932040.26286@g5.osdl.org> (raw)
In-Reply-To: <442213F4.7040603@op5.se>
On Thu, 23 Mar 2006, Andreas Ericsson wrote:
>
> <sidenote>
> I've never understood what orthogonal means in this sense. "at a right angle"
> as in flagging for attention or the exactly counter-productive to what one
> should use?
> </sidenot>
No. Orthogonal in math may be literally "straight angle", but in
non-geometric speak it means "independent" or "statistically unrelated".
See
http://wordnet.princeton.edu/perl/webwn?s=orthogonal
and the two first definitions in particular.
Ie two issues (or, in this case, "branches") are orthogonal if they have
nothing in common - they fix two totally independent things.
This is, btw, totally consistent with the geometric meaning of the word.
Two vectors are orthogonal if they have no common component: the dot
product is zero (ie the projection of one vector onto another is the null
vector).
So if you see two lines of development as being "vectors" from a common
source, when they have nothing in common, they are orthogonal.
Of course, the development space is neither three-dimensional nor
euclidian, so it's a strange kind of vector, but still ;)
Linus
prev parent reply other threads:[~2006-03-23 3:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 19:28 Best way to generate a git tree containing only a subset of commits from another tree? Anton Altaparmakov
2006-03-22 21:28 ` Radoslaw Szkodzinski
2006-03-23 0:25 ` Petr Baudis
2006-03-23 0:44 ` Andreas Ericsson
2006-03-23 1:38 ` Junio C Hamano
2006-03-23 3:20 ` Andreas Ericsson
2006-03-23 3:43 ` Linus Torvalds [this message]
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=Pine.LNX.4.64.0603221932040.26286@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=ae@op5.se \
--cc=aia21@cam.ac.uk \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).