From: "Bo Ørsted Andresen" <bo.andresen@zlin.dk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] portage and rsync vs svn
Date: Mon, 19 Jun 2006 12:13:42 +0200 [thread overview]
Message-ID: <200606191213.53725.bo.andresen@zlin.dk> (raw)
In-Reply-To: <9b1675090606190158r260b6340q2c009f0cb83a68b0@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
On Monday 19 June 2006 10:58, Trenton Adams wrote:
> > > One other benefit of this mechanism, that I can think of, would be
> > > that I could easily roll back to my last sync date or release, if some
> > > of the updated ebuilds caused me problems.
> >
> > That really should not be necessary. What you should of course do is file
> > a bug so the problems can be fixed for everyone.
>
> Well, one problem I had was not actually *really* bug. It was a
> requirement that I did not fulfill, but was unable to figure it out
> instantly. So, rolling back would have been very useful at that time.
> It would just add another level of safety.
If an ebuild is removed from the tree while you still need it then chances are
that others need it too. Then it is indeed a bug. If you need an ebuild that
has been removed from the tree it is available from the cvs [1]. As mentioned
in my previous mail cvs is going to be replaced by a superior VCS hopefully
within this year.
[1] http://www.gentoo.org/cgi-bin/viewcvs.cgi
--
Bo Andresen
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-06-19 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 7:58 [gentoo-user] portage and rsync vs svn Trenton Adams
2006-06-19 8:50 ` Bo Ørsted Andresen
2006-06-19 8:58 ` Trenton Adams
2006-06-19 10:13 ` Bo Ørsted Andresen [this message]
2006-06-19 20:15 ` Trenton Adams
2006-06-19 21:52 ` Bo Ørsted Andresen
2006-06-19 21:59 ` Teresa and Dale
2006-06-20 5:26 ` Trenton Adams
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=200606191213.53725.bo.andresen@zlin.dk \
--to=bo.andresen@zlin.dk \
--cc=gentoo-user@lists.gentoo.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