From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Where can I find "recent" qemu out-of-tree ebuild
Date: Thu, 26 Oct 2017 00:54:05 -0400 [thread overview]
Message-ID: <20171026045405.GA22018@waltdnes.org> (raw)
In-Reply-To: <d9848385-9a7f-74c0-979a-68704c0a92fa@gentoo.org>
On Wed, Oct 25, 2017 at 09:51:21PM -0400, Michael Orlitzky wrote
> On 10/25/2017 09:24 PM, Walter Dnes wrote:
> > What's with the big gap, and where can I find more
> > recent out-of-tree ebuilds?
>
> The big gap is because we stopped using CVS back then. Gitweb is being
> real slow right now, but you can usually browse around the tree at
> various commits to find old versions of files. Try this for -r55:
>
> https://gitweb.gentoo.org/repo/gentoo.git/tree/app-emulation/qemu?id=4716c9ae8666e4cfc6eff46960f7bff8f4f3d708
Next question... from a git newbie... is there a way to pull down the
entire "files" directory with patches in one command? gitweb seems to
delight in using tons of fancy HTML to format a cute layout. Right-
clicking on the directory points to a cutsie layout. If I force it to
"plain", I get a list of 20 files. I suppose I could click on each file
and copy-paste text to a similarly-named file on my machine,
rinse-lather-repeat 20 times, but that's rather painful.
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
next prev parent reply other threads:[~2017-10-26 4:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 1:24 [gentoo-user] Where can I find "recent" qemu out-of-tree ebuild Walter Dnes
2017-10-26 1:51 ` Michael Orlitzky
2017-10-26 3:15 ` Walter Dnes
2017-10-26 4:54 ` Walter Dnes [this message]
2017-10-26 11:40 ` Rich Freeman
2017-10-26 13:28 ` Walter Dnes
2017-10-26 13:55 ` Rich Freeman
2017-10-26 16:18 ` Walter Dnes
2017-10-26 16:35 ` Rich Freeman
2017-10-26 22:29 ` [gentoo-user] [SOLVED] " Walter Dnes
2017-10-26 1:58 ` [gentoo-user] " Lucas Ramage
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=20171026045405.GA22018@waltdnes.org \
--to=waltdnes@waltdnes.org \
--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