From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 014 release
Date: Thu, 22 Jan 2004 20:32:49 +0000 [thread overview]
Message-ID: <20040122203249.GA1785@vrfy.org> (raw)
In-Reply-To: <20040122181550.GA14725@kroah.com>
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.
Kay
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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
next prev parent reply other threads:[~2004-01-22 20:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 18:15 [ANNOUNCE] udev 014 release 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 [this message]
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
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=20040122203249.GA1785@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 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 NNTP newsgroup(s).