From: newsham@lava.net (Tim Newsham)
Subject: [Unix-jun72] Another reorganisation suggestion
Date: Sun, 4 May 2008 14:03:04 -1000 (HST) [thread overview]
Message-ID: <Pine.BSI.4.64.0805041401090.20114@malasada.lava.net> (raw)
In-Reply-To: <20080504224125.GB63333@minnie.tuhs.org>
> early C compilers to work. Could I suggest that we make a src/ directory
> in svn, which will hold any source code that produces V1/V2 executables?
Sure. just make the directory and add files to it and "svn add dir"
or "svn mkdir dir" and start adding files. Either way, once you commit
it'll get pushed up.
> Which of course implies that we might need to rename rebuilt/ to sys/ :-)
I'm fine renaming things.. the early names were just kind of ad hoc.
though "rebuilt" should probably be named "clean" and the "build"
directory that has the patches applied should probably be "sys".
> Warren
Tim Newsham
http://www.thenewsh.com/~newsham/
prev parent reply other threads:[~2008-05-05 0:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 22:41 Warren Toomey
2008-05-05 0:03 ` Tim Newsham [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=Pine.BSI.4.64.0805041401090.20114@malasada.lava.net \
--to=newsham@lava.net \
/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).