From: Jonathan Larmour <jifl@jifvik.org>
To: Sergei Gavrikov <sergei.gavrikov@gmail.com>,
eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: eCos CVS import issue
Date: Sun, 26 Oct 2014 19:32:00 -0000 [thread overview]
Message-ID: <544D4C38.8050401@jifvik.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1410252144220.10520@sg-laptop>
On 25/10/14 21:14, Sergei Gavrikov wrote:
> Hi
>
> From time to time I do import eCos CVS sources to my local Fossil
> (http://fossil-scm.org) repository using Jörg's Sonnenberg
> (http://www.sonnenberger.org/) `cvs2fossil' engine.
>
> There are two ,v files in CVS Attic directory (recently appeared) which
> break the import. The files are
>
> % find -regex '.*\/Attic\/.*v' -printf 'test -e %h/../%f && echo %p\n'|sh
> ecos/packages/hal/cortexm/kinetis/twr_k60n512_fxm/current/include/pkgconf/Attic/mlt_kinetis_flash_sram2s_ram.ldi,v
> ecos/packages/hal/cortexm/kinetis/twr_k60n512_fxm/current/include/pkgconf/Attic/mlt_kinetis_flash_sram2s_ram.h,v
>
> A question to CVS gurus, May these files exist if the files with the
> same names are exist under CVS?
I don't know why you're seeing that - the files do not exist under CVS, only
in the Attic (which is where files are put when they are deleted, although
it's also used if files live only on a branch, not the trunk... in this case
the files _were_ deleted though). If I run your exact command here, I get no
output.
Also the files don't seem to have changed recently either. The last change in
that directory was June 2nd 2013. So I think your import process has gone
wrong somewhere, sorry.
Jifl
next prev parent reply other threads:[~2014-10-26 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 19:15 Sergei Gavrikov
2014-10-26 19:32 ` Jonathan Larmour [this message]
2014-10-27 6:42 ` Sergei Gavrikov
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=544D4C38.8050401@jifvik.org \
--to=jifl@jifvik.org \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=sergei.gavrikov@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).