From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 014 release
Date: Fri, 20 Feb 2004 02:01:43 +0000 [thread overview]
Message-ID: <20040220020143.GA13091@vrfy.org> (raw)
In-Reply-To: <20040122181550.GA14725@kroah.com>
On Thu, Jan 22, 2004 at 01:06:21PM -0800, Greg KH wrote:
> On Thu, Jan 22, 2004 at 09:32:49PM +0100, Kay Sievers wrote:
> > On Thu, Jan 22, 2004 at 07:28:13PM +0100, Måns Rullgård wrote:
> > > Greg KH <greg@kroah.com> writes:
> > >
> > > > udev development is done in a BitKeeper repository located at:
> > > > bk://linuxusb.bkbits.net/udev
> > >
> > > Why do I have to do bk pull twice to get updates from that repository?
> > > Like this:
> > >
> > > $ bk pull
> > > Pull bk://linuxusb.bkbits.net/udev
> > > -> file://home/src/udev
> > > $ bk pull
> > > Pull bk://linuxusb.bkbits.net/udev
> > > -> file://home/src/udev
> > > ---------------------- Receiving the following csets -----------------------
> > > 1.449 1.448 1.447 1.446 1.445 1.444 1.443 1.442 1.441 1.440
> > > ----------------------------------------------------------------------------
> >
> > I have exactly the same behavior. Three out of ten times,
> > I have to pull twice to get it.
>
> Very wierd. Make sure you are using the latest version of bk (3.0.4 as
> of today). I've pushed a single changeset out to the repository for
> everyone to see if they can pull successfully.
Today I got the same wierd thing again.
Anybody with still the same problem?
thanks,
Kay
kay@pim:~/src$ cd udev
kay@pim:~/src/udev$ bk pull
Pull bk://linuxusb.bkbits.net/udev/
-> file://home/kay/src/udev
kay@pim:~/src/udev$
kay@pim:~/src/udev$
kay@pim:~/src/udev$ bk pull
Pull bk://linuxusb.bkbits.net/udev/
-> file://home/kay/src/udev
---------------------- Receiving the following csets-----------------------
1.585 1.584 1.583 1.582 1.581 1.580 1.579 1.578 1.577 1.576
1.575
----------------------------------------------------------------------------
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&opÌk
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-02-20 2:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 18:15 [ANNOUNCE] udev 014 release Greg KH
2004-01-22 18:15 ` Greg KH
2004-01-22 18:28 ` Måns Rullgård
2004-01-22 20:17 ` Greg KH
2004-01-22 20:24 ` Måns Rullgård
2004-01-22 20:32 ` Kay Sievers
2004-01-22 20:35 ` Hanna Linder
2004-01-22 21:06 ` Greg KH
2004-01-22 21:08 ` Måns Rullgård
2004-01-22 21:18 ` Kay Sievers
2004-01-22 21:20 ` Måns Rullgård
2004-02-20 2:01 ` Kay Sievers [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=20040220020143.GA13091@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
/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.