From: Michael Ang <mang@subcarrier.org>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] branching HOW(NOT)TO
Date: Tue, 29 Feb 2000 15:17:57 -0500 [thread overview]
Message-ID: <38BC2975.CCAB5108@subcarrier.org> (raw)
Just a short note on branching. If you are thinking about creating a
branch, you should know that branching/merging is one of the weakest
parts of CVS.
For branching I would like to establish the following conventions. For
branch "foo" there will be a static FOO_BASE tag that marks the
beginning of the branch, and development will be done using the
FOO_BRANCH tag. The static tag is crucial for later merging.
Using all caps is ugly but helps to distinguish between directory names
and tags names on the command line. (This is a weak protection, but
helps when you're playing with tags at 3am in the morning.)
- Mike.
reply other threads:[~2000-02-29 21:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=38BC2975.CCAB5108@subcarrier.org \
--to=mang@subcarrier.org \
--cc=parisc-linux@thepuffingroup.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.