lkml.org 
[lkml]   [2003]   [Jul]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Strange BK behaviour?
On Fri, Jul 11, 2003 at 03:54:40PM -0400, Ben Collins wrote:
> On Fri, Jul 11, 2003 at 01:55:32PM -0700, Larry McVoy wrote:
> > Ahh, it's there, bkbits just isn't showing it because it is an empty merge
> > changeset. That's a bug. If you care, file a bug on bk/web with a
> > summary like "show merge changesets if they are tagged".
>
> It definitely got down to CVS/SVN.

Right, the data is there. There is a lot of "merge noise" in BK where BK
is just recording the fact that changes in unrelated files have been
brought together. In general, you don't want to see all that noise, it's
more or less internal BK metadata. So BK/Web filters it out, as does
bk changes. But in this case, because the cset in question is "named"
with a tag it should have been shown.

It's a presentation issue, not a data problem, which is why CVS/SVN saw
it - the exporter works on the raw data.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:46    [W:0.032 / U:0.120 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site