All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Johansson <kenneth.johansson@etx.ericsson.se>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: Problems with cvs-access
Date: 04 Jul 2003 13:28:13 +0200	[thread overview]
Message-ID: <1057318093.3430.71.camel@spawn> (raw)
In-Reply-To: <20030703170412.56482C6D82@atlas.denx.de>

On Thu, 2003-07-03 at 19:04, Wolfgang Denk wrote:
> Dear Juergen,
> 
> in message <OF2C7F932A.450ECC64-ONC1256D58.00532B9B@phytec.de> you wrote:
> > 
> > i've tried to get the latest version of u-boot via cvs..
> > It seems that there is a lock file #cvs.lock in the directory
> > u-boot/board/eltec
> > 
> > Can you check this ?
> 
> I can confirm the problem, but I cannot  help  it.  Please  submit  a
> support request to SourceForge.
> 
> > I've also tried to get the latest tarball. But the tarball is from
> > Monday...
> > I thought the tarball should be generated every night.
> 
> It _should_ get generated each night. But it seems SF  is  hopelessly
> overloaded.  Please complain about the problems to SF. If more people
> complain they might start doing something.

One thing would be to switch over to http://savannah.gnu.org/
It is very similar to sf.net.

Personally I would not complain going to http://bkbits.net/ and using
bitkeeper. I think it works really well for the kernel. And more or less
anyone doing work on u-boot already use it. There are bk->cvs gateway
for the few who won't for "religious" reasons.


-- 
Kenneth Johansson	
Ericsson AB                       Tel: +46 8 719 70 20
Tellusborgsv?gen  90              Fax: +46 8 719 29 45
126 25 Stockholm                  ken at switchboard.ericsson.se

  reply	other threads:[~2003-07-04 11:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-03 15:17 [U-Boot-Users] Problems with cvs-access J.Kilb at phytec.de
2003-07-03 17:04 ` [U-Boot-Users] " Wolfgang Denk
2003-07-04 11:28   ` Kenneth Johansson [this message]
2003-07-06 16:40     ` Wolfgang Denk

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=1057318093.3430.71.camel@spawn \
    --to=kenneth.johansson@etx.ericsson.se \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.