From: Rob Browning <rlb@defaultvalue.org>
Cc: mvo@zagadka.ping.de, evan@glug.org, guile-devel@gnu.org
Subject: Re: More Bug Stuff
Date: Mon, 25 Mar 2002 09:48:08 -0600 [thread overview]
Message-ID: <87bsdck5s7.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <E16pPjO-0006vO-00@giblet> (Thien-Thi Nguyen's message of "Mon, 25 Mar 2002 00:21:30 -0800")
Thien-Thi Nguyen <ttn@giblet.glug.org> writes:
> on the other hand, single file at top is simple and here. so really, my
> proposal (now -- please ignore previous) comes down to:
>
> N -- the rfc822 for bug N
> .N -- the directory w/ all of bug N's related files;
> may be empty or absent
>
> in the headers, this would add required header:
>
> bug-stuff-dir: .N
>
> under .N things can be named in regular ways, such as "test-case-1.scm"
> or "why-i-must-rant-against-this-bug" or "rfc822" (symlink). the naming
> of these files can be conventionalized later and w/o overmuch regard to
> the actual bug number. programs that munge these files are accordingly
> lightened. programs that munge bug sets need to stay informed w/
> `bug-stuff-dir' but that's just another header (already done).
I really don't like the idea of hidden directories with potentially
critical information. If we are going to have per-bug directories
could we choose an arrangement that sorts a bug and all its attendant
data together in an ls listing? I don't have strong prefs, but as an
random place to start, why not:
N-info
N-dir/
ls does the right thing, and you can ignore all the -dir files if you
want to with a simple "grep -v", or even "ls *-[^d]*" or similar, and
you can make sure to copy all of a bug's related info via "cp -a N-*
dest".
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-25 15:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-24 20:23 More Bug Stuff Evan Prodromou
2002-03-24 23:03 ` Marius Vollmer
2002-03-25 8:21 ` Thien-Thi Nguyen
2002-03-25 15:48 ` Rob Browning [this message]
2002-03-25 21:19 ` Thien-Thi Nguyen
2002-03-25 21:35 ` Marius Vollmer
2002-03-25 22:00 ` Thien-Thi Nguyen
2002-03-25 22:03 ` Thien-Thi Nguyen
2002-03-25 22:25 ` Marius Vollmer
2002-03-27 0:31 ` Evan Prodromou
2002-03-27 2:58 ` Thien-Thi Nguyen
2002-03-27 19:09 ` Marius Vollmer
2002-03-27 20:39 ` Thien-Thi Nguyen
2002-04-07 11:17 ` Marius Vollmer
2002-04-07 19:05 ` Thien-Thi Nguyen
2002-04-07 21:22 ` Thien-Thi Nguyen
2002-04-07 21:38 ` Marius Vollmer
2002-03-27 18:56 ` Marius Vollmer
2002-03-28 16:52 ` Evan Prodromou
2002-03-29 4:02 ` Thien-Thi Nguyen
2002-04-07 12:03 ` Marius Vollmer
2002-04-07 22:22 ` Thien-Thi Nguyen
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bsdck5s7.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=evan@glug.org \
--cc=guile-devel@gnu.org \
--cc=mvo@zagadka.ping.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).