From: Natanael Olaiz <nolaiz@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] eclass history
Date: Mon, 16 Apr 2012 12:53:16 +0200 [thread overview]
Message-ID: <CAP=gXz7LDEt1i11P3Xw=dzP6XRRJjd5Uei2MfGNxu8MiJMQN8A@mail.gmail.com> (raw)
In-Reply-To: <CAKmKYaAj+oGZ4=OOyxrr-EJwvEogu2F57t3HMOUZAtLu3MTd_A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
Thanks!
On 16 April 2012 12:43, Dirkjan Ochtman <djc@gentoo.org> wrote:
> On Mon, Apr 16, 2012 at 12:37, Natanael Olaiz <nolaiz@gmail.com> wrote:
> > I want to debug this, because for me (that have to work with this) is a
> real
> > PITA.... My question is : where I can see the history of the eclasses?
> Some
> > time ago all worked perfect! But with the rsync I have no idea what is
> going
> > on, I don't know the history (and all local changes are lost each
> > --rsync...)
>
> Start here:
>
>
> http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/eclass/subversion.eclass?view=log
>
> (Of course, you can also get a checkout via anonymous CVS, but cvs is
> slow PITA.)
>
> Cheers,
>
> Dirkjan
>
>
[-- Attachment #2: Type: text/html, Size: 1192 bytes --]
prev parent reply other threads:[~2012-04-16 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 10:37 [gentoo-dev] eclass history Natanael Olaiz
2012-04-16 10:43 ` Dirkjan Ochtman
2012-04-16 10:53 ` Natanael Olaiz [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='CAP=gXz7LDEt1i11P3Xw=dzP6XRRJjd5Uei2MfGNxu8MiJMQN8A@mail.gmail.com' \
--to=nolaiz@gmail.com \
--cc=gentoo-dev@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