From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch 0/5 salinfo-0.6] summary
Date: Tue, 05 Oct 2004 01:42:08 +0000 [thread overview]
Message-ID: <3546.1096940528@kao2.melbourne.sgi.com> (raw)
In-Reply-To: <11145.1096870990@kao2.melbourne.sgi.com>
On Mon, 4 Oct 2004 10:02:18 -0600,
Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
>By the way, I hear grumbling from neighboring cubes about
>the colons in the log file names, because it makes it hard
>to move the files to Windows (HP's log analysis tools are
>Windows-based).
>
>How much of a hassle would it be if we changed the colons
>to underscores or something?
Windows - yuck!
Do you want to add this to 0.6 or bump the version to 0.7?
Index: salinfo-0.6/salinfo_decode.c
=================================--- salinfo-0.6.orig/salinfo_decode.c Mon Oct 4 16:04:03 2004
+++ salinfo-0.6/salinfo_decode.c Tue Oct 5 10:49:38 2004
@@ -260,7 +260,7 @@ talk_to_sal (const char *type, const cha
for (suffix = 0; ; ++suffix) {
snprintf(filename, sizeof(filename),
- "%s/raw/%02x%02x-%02x-%02x-%02x:%02x:%02x-cpu%d-%s.%d",
+ "%s/raw/%02x%02x-%02x-%02x-%02x_%02x_%02x-cpu%d-%s.%d",
directory,
buffer->timestamp.slh_century,
buffer->timestamp.slh_year,
@@ -291,7 +291,7 @@ talk_to_sal (const char *type, const cha
close(fd);
snprintf(filename, sizeof(filename),
- "%s/decoded/%02x%02x-%02x-%02x-%02x:%02x:%02x-cpu%d-%s.%d",
+ "%s/decoded/%02x%02x-%02x-%02x-%02x_%02x_%02x-cpu%d-%s.%d",
directory,
buffer->timestamp.slh_century,
buffer->timestamp.slh_year,
next prev parent reply other threads:[~2004-10-05 1:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 6:23 [patch 0/5 salinfo-0.6] summary Keith Owens
2004-10-04 15:45 ` Bjorn Helgaas
2004-10-04 16:02 ` Bjorn Helgaas
2004-10-05 1:42 ` Keith Owens [this message]
2004-10-05 15:44 ` Bjorn Helgaas
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=3546.1096940528@kao2.melbourne.sgi.com \
--to=kaos@sgi.com \
--cc=linux-ia64@vger.kernel.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