From: Catalin Marinas <catalin.marinas@arm.com>
To: Stelian Pop <stelian.pop@fr.alcove.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Larry McVoy <lm@bitmover.com>
Subject: Re: BKCVS broken ?
Date: Thu, 17 Mar 2005 15:43:54 +0000 [thread overview]
Message-ID: <tnxd5tymg5h.fsf@arm.com> (raw)
In-Reply-To: <20050317144522.GK22936@hottah.alcove-fr> (Stelian Pop's message of "Thu, 17 Mar 2005 15:45:22 +0100")
Stelian Pop <stelian.pop@fr.alcove.com> wrote:
> The current bkcvs export is broken, several recent changesets are
> missing from it.
>
> This occurs at least in the mm/ directory, but I haven't verified
> if other directories are not affected. I detected this problem
> because the head of bkcvs doesn't compile anymore and shows errors
> in mm/* missing symbols.
I noticed a similar problem a few days ago. The ChangeSet,v file
contained the logs but there were no files with the corresponding
(Logical change ...). A day later, the files corresponding to those
logs were updated. I initially blamed the non-atomicity of CVS and
rsync but, reading your e-mail, the problem might not be that simple.
BTW, is there a way for the ChangeSet,v file to be updated after all
the source files are updated (to avoid the empty patch problem if
rsync'ing when the BKCVS repository is updated)?
Catalin
next prev parent reply other threads:[~2005-03-17 15:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 14:45 BKCVS broken ? Stelian Pop
2005-03-17 15:43 ` Catalin Marinas [this message]
2005-03-17 15:44 ` Larry McVoy
2005-03-18 3:07 ` H. Peter Anvin
2005-03-18 0:10 ` Larry McVoy
2005-03-18 5:50 ` Erik Andersen
2005-03-18 6:38 ` Larry McVoy
2005-03-18 9:00 ` Stelian Pop
2005-03-18 14:13 ` Larry McVoy
2005-03-18 14:21 ` Stelian Pop
2005-03-18 15:08 ` Hong Kong Phoey
2005-03-18 22:09 ` Stelian Pop
2005-03-19 14:52 ` Larry McVoy
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=tnxd5tymg5h.fsf@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=stelian.pop@fr.alcove.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