From: Christopher Faylor <me@cgf.cx>
To: overseers@sourceware.org
Subject: Re: Update subversion?
Date: Tue, 15 Aug 2006 04:40:00 -0000 [thread overview]
Message-ID: <20060815041010.GB7123@trixie.casa.cgf.cx> (raw)
In-Reply-To: <44E1425F.1000709@dberlin.org>
On Mon, Aug 14, 2006 at 11:41:19PM -0400, Daniel Berlin wrote:
>Christopher Faylor wrote:
>> up2date is claiming that there is a new version of subversion available.
>>
>> Is it ok to update this Dan?
>
>Don't.
>We're using the official rpm specs to build rpms of subversion.
>
>We also have a few performance patches that are part of a later version
>(1.4.0) in our 1.3.x build that we'd lose.
Ok. That's what I thought. I probably should have known this and I probably
will be asking some variation of this question in the future. :-)
>Subversion is going to release a new version (1.4.0) in a few weeks anyway.
>
>The update is probably to 1.3.x, which is a bugfix release of the 1.3.x
>series, and doesn't contain anything we really care about :)
Yes.
subversion 1.3.2 0.1.el4.rf i386
subversion-devel 1.3.2 0.1.el4.rf i386
subversion-perl 1.3.2 0.1.el4.rf i386
I came >this< close to just typing "up2date -u" and just letting it churn.
I guess I'll try to fake an update without changing any files to avoid that
particular mistake.
Thanks.
cgf
next prev parent reply other threads:[~2006-08-15 4:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 4:10 Christopher Faylor
2006-08-15 4:37 ` Daniel Berlin
2006-08-15 4:40 ` Christopher Faylor [this message]
2006-08-15 12:45 ` Daniel Berlin
2006-08-15 16:49 ` Christopher Faylor
2006-08-15 18:51 ` Frank Ch. Eigler
2006-08-17 17:12 ` Christopher Faylor
2006-08-17 17:24 ` Daniel Berlin
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=20060815041010.GB7123@trixie.casa.cgf.cx \
--to=me@cgf.cx \
--cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).