From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Brian Youmans <3diff@gnu.org>, gdb@sources.redhat.com
Subject: Re: [Fwd: Cron <gdbadmin@sources> sh $HOME/ss/do-all-gdb-snapshots]
Date: Mon, 21 Jan 2002 08:24:00 -0000 [thread overview]
Message-ID: <3C4C40B7.2070803@cygnus.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020121115543.16755J-100000@is>
> What am I missing?
Probably nothing. I agree, CVS can be pretty counter intuitive.
> One of the things I can never remember is when do you have to use the
> "-r TAG" switch with CVS commands issued on the branch. So I tend to
> always use that switch, which is perhaps incorrect with "cvs add".
CVS should see that the directory is on a branch and remember to add new
files to that same branch. There were definitly bugs on this (I
remember being tripped my self a few years back and that led to a bug
fix). You're sequence likely ticked another of them and sccrambled the
contents of the CVS directory.
All I did was:
cvs add foo
cvs commit
in my 5.1 tree.
>> Should the FDL and ``Free Software Needs Free Documentation'' blurbs be
>> added to the GDB Internals Manual?
>
>
> I asked Richard Stallman, and he replied that it's okay to have only
> one FDL in a collection of documents that are distributed together.
> The same situation exists with Emacs, so we are in a good company ;-)
M'kay.
>> Also, should the main GDB manual include a printed copy of the GPL.
>
>
> I don't know. In general, GDB is considered one of the few
> ``important packages'' that are part of GNU software, so having the
> GPL in the manual is probably a good idea. GCC, for example, does
> have such a section. And we even have a section for it ("Free
> Software"), which now just tells what the GPL is.
Ok.
Andrew
next prev parent reply other threads:[~2002-01-21 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-20 20:27 Andrew Cagney
2002-01-21 1:57 ` Eli Zaretskii
2002-01-21 8:24 ` Andrew Cagney [this message]
2002-01-22 8:56 ` Brian Youmans
2002-01-22 10:39 ` 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=3C4C40B7.2070803@cygnus.com \
--to=ac131313@cygnus.com \
--cc=3diff@gnu.org \
--cc=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox