From: Larry McVoy <lm@bitmover.com>
To: Ben Collins <bcollins@debian.org>
Cc: Larry McVoy <lm@bitmover.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Strange BK behaviour?
Date: Fri, 11 Jul 2003 14:26:45 -0700 [thread overview]
Message-ID: <20030711212645.GA17601@work.bitmover.com> (raw)
In-Reply-To: <20030711195440.GY439@phunnypharm.org>
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
prev parent reply other threads:[~2003-07-11 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 20:21 Strange BK behaviour? Marcelo Tosatti
2003-07-11 20:55 ` Larry McVoy
2003-07-11 19:54 ` Ben Collins
2003-07-11 21:26 ` Larry McVoy [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=20030711212645.GA17601@work.bitmover.com \
--to=lm@bitmover.com \
--cc=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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