From: Bob Rogers <rogers-emacs@rgrjr.dyndns.org>
Cc: Nick Roberts <nickrob@snap.net.nz>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: `smoothing_enabled' undeclared
Date: Mon, 3 Jul 2006 11:40:28 -0400 [thread overview]
Message-ID: <17577.14956.926393.599508@rgrjr.dyndns.org> (raw)
In-Reply-To: <87bqs7shtn.fsf@catnip.gol.com>
From: Miles Bader <miles@gnu.org>
Date: Mon, 03 Jul 2006 08:33:24 +0900
Nick Roberts <nickrob@snap.net.nz> writes:
> > Every branch has a "head". The main branch is called "the trunk".
>
> HEAD is a tag. Is it a tag for the head of the trunk or the head of the
> branch which the working directory is in?
The CVS docs are maddeningly vague about this...
I thought it was the latter, but I just did a bit of testing, and the
result of using -rHEAD is different depending on which command you use.
. . .
* "cvs update -rHEAD src/xfaces.c" _changes_ the sticky tag from the
file to be "HEAD", and updates it to be the latest revision on
_the trunk_.
It's even worse than that. If you edit src/xfaces.c, you'll find you
can't commit the change; you must first do "cvs update -A src/xfaces.c"
to get it fully back onto the trunk. If you look at emacs/CVS/Entries,
you'll notice that "trunk" is denoted by the absence of a tag (field
between the last two slashes), not an explicit "HEAD".
IMHO, "-rHEAD" is strictly to be avoided.
-- Bob Rogers
http://rgrjr.dyndns.org/
next prev parent reply other threads:[~2006-07-03 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 3:20 `smoothing_enabled' undeclared Herbert Euler
2006-06-23 10:10 ` Eli Zaretskii
2006-06-24 2:16 ` Herbert Euler
2006-06-24 2:38 ` Nick Roberts
2006-07-02 16:13 ` Stefan Monnier
2006-07-02 22:51 ` Nick Roberts
2006-07-02 23:33 ` Miles Bader
2006-07-03 15:40 ` Bob Rogers [this message]
2006-07-06 22:27 ` Stefan Monnier
2006-06-24 6:27 ` Eli Zaretskii
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=17577.14956.926393.599508@rgrjr.dyndns.org \
--to=rogers-emacs@rgrjr.dyndns.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=nickrob@snap.net.nz \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.