[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnu-arch-users] Tutorial question
From: |
Pierce T . Wetter III |
Subject: |
[Gnu-arch-users] Tutorial question |
Date: |
Tue, 24 Feb 2004 10:31:44 -0700 |
"An archive name consists of an email address, followed by two dashes,
followed by a suffix."
Is that a requirement (name is parsed) or a "best practice"?
would:
pierce--projects
work? (That's enough for internal people to find me.)
What about:
customer1--2004 (Ignore best practice, use customer name instead)
or
projects-2004 (archive is really just an arbitrary name, its
just
a best practice to include email)
Heres how I might change this:
Usage:
It's best to use your email address with two dashes, followed by a
name for the archive itself. That way your particular archive is
associated with you, and if you share your archive with someone else,
they'll know where it came from if it appears on their disk.
The archive name itself can be anything, though it shouldn't have two
dashes. With arch, you can have one archive that holds ALL of your
projects, or you can break them up into multiple archives. Since an
archive holds quite a bit of history, you often want to split your
archives at various points in time, so most people include some kind of
timestamp.
Typical examples:
One giant archive to hold all projects (note split on year):
address@hidden
address@hidden
This is typical for most people, since its convenient to have all
your
source in one place.
Archive per customer:
address@hidden
address@hidden
address@hidden
In this case, fred and barney have quite different projects, so it
makes sense
to separate their archives.
You can mix and match these strategies of course:
address@hidden
address@hidden (big archives for work)
address@hidden (open source project you're
contributing to)
Pierce
- [Gnu-arch-users] Tutorial question,
Pierce T . Wetter III <=