From: Linus Torvalds <torvalds@osdl.org>
To: "Robin Rosenberg (list subscriber)" <robin.rosenberg.lists@dewire.com>
Cc: git@vger.kernel.org
Subject: Re: cvsps wierdness
Date: Mon, 12 Jun 2006 14:30:47 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0606121429510.5498@g5.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0606121406200.5498@g5.osdl.org>
On Mon, 12 Jun 2006, Linus Torvalds wrote:
>
> I don't think this is strictly correct, btw. I suspect you can still get
> into strange situations where the changeset merging has resulted in one
> file ordering one way, and another file ordering the other way.
Btw, I also fear that this could make cvsps noticeably slower, since the
patchset comparison code is pretty expensive (O(n*m) in files in each
patch-set).
Linus
next prev parent reply other threads:[~2006-06-12 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 20:47 cvsps wierdness Robin Rosenberg (list subscriber)
2006-06-12 21:27 ` Linus Torvalds
2006-06-12 21:30 ` Linus Torvalds [this message]
2006-06-13 6:06 ` Robin Rosenberg (list subscriber)
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.0606121429510.5498@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg.lists@dewire.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).