From: merlyn at stonehenge.com (Randal L. Schwartz)
Subject: can't get snapshots to work in v0.9.0.3-4-gf50b
Date: Thu, 03 May 2012 16:18:03 -0700 [thread overview]
Message-ID: <86pqakhn10.fsf@red.stonehenge.com> (raw)
In-Reply-To: <86aa1phqp0.fsf@red.stonehenge.com>
>>>>> "Randal" == Randal L Schwartz <merlyn at stonehenge.com> writes:
Randal> I pulled the latest stable (v0.9.0.3-4-gf50b), and I can't seem to get
Randal> snapshots to show up on the web pages. They can be pulled by entering
Randal> the URL directly, but without a ui, it's a bit hard to find.
Randal> Is this known?
Randal> I'm using scan-path, and yes, I'm setting snapshots=tar.gz zip
Randal> before the scan-path.
Argh. For some reason, I expected them to show up on the summary page
next to the branch name. Apparently, no, they're only on the commit
page.
Duh.
All better.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn at stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.posterous.com/ for Smalltalk discussion
prev parent reply other threads:[~2012-05-03 23:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 21:58 merlyn
2012-05-03 23:18 ` merlyn [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=86pqakhn10.fsf@red.stonehenge.com \
--to=cgit@lists.zx2c4.com \
/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).