[Fwd: Cron <gdbadmin@sources> sh $HOME/ss/do-all-gdb-snapshots]

[Fwd: Cron <gdbadmin@sources> sh $HOME/ss/do-all-gdb-snapshots]

[Andrew Cagney]

Eli,

FYI, you were right, CVS doesn't like you! :=)  I think I've tweeked 
things on the branch.  The next update is in ~24 hrs so we'll find out then.
http://sources.redhat.com/ml/gdbadmin/2002-01/msg00019.html

Eli, Brian,

Should the FDL and ``Free Software Needs Free Documentation'' blurbs be 
added to the GDB Internals Manual?  I don't expect the FSF to ever 
publish the internals manual so it probably doesn't matter.

Also, should the main GDB manual include a printed copy of the GPL. 
While probably not strictly needed I'm wondering if it should be 
included for completeness.

(perhaphs I should just keep quiet :-)

Andrew

Re: [Fwd: Cron <gdbadmin@sources> sh $HOME/ss/do-all-gdb-snapshots]

[Eli Zaretskii]

On Sun, 20 Jan 2002, Andrew Cagney wrote:

> FYI, you were right, CVS doesn't like you! :=)

Probably my fault, at least to some extent, but my opinion that the
CVS has several counter-intuitive aspects in its UI has until now
fallen on deaf ears (yes, I actually spoke to some of the CVS
developers and was told that I didn't understand ``the CVS way'').

Anyway, how do you add a new file on a branch?

What happened to me is that I had no problems with "cvs add" on the
trunk, followed by "cvs ci" on the trunk.  On the branch, I think I
mistakenly typed "cvs ci" first, without having fdl.texi present in
the directory, and was told that ``a newly born fdl.texi
disappeared''.  I then remembered that I missed "cvs add" and did
that, only to be told that ``someone else already added it''.  After
that, "cvs ci" refused to work, demanding that I do "cvs add" first...

What am I missing?

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".

> 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 ;-)

> 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.

Re: [Fwd: Cron <gdbadmin@sources> sh $HOME/ss/do-all-gdb-snapshots]

[Andrew Cagney]

> 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

Re: [Fwd: Cron <gdbadmin@sources> sh $HOME/ss/do-all-gdb-snapshots]

[Brian Youmans]

If the Internals Manual is a separate document that is usually used
and/or printed separately from the main GDB manual, and it is at
least, say, 20 pages, , it should have a separate FDL permission
notice and copy of the FDL.  This can simply be an @include fdl.texi
since the FDL is in the GDB distribution already.  If this is usually
just a chapter in the main manual, it doesn't need a separate copy of
the FDL.

As to the GPL - that is a political and authorial decision - is it
useful practically and/or politically to give people a copy of the GPL
in the manual?  I think RMS has said in the past that he thinks the
major GNU manuals should include a copy.  Ask him if you want, but it
is probably a good idea.  Not required by license, but a good idea.

- Brian Y., FSF

Re: [Fwd: Cron <gdbadmin@sources> sh $HOME/ss/do-all-gdb-snapshots]

[Eli Zaretskii]

> From: Brian Youmans <3diff@gnu.org>
> Date: Tue, 22 Jan 2002 11:56:23 -0500
> 
> If the Internals Manual is a separate document that is usually used
> and/or printed separately from the main GDB manual, and it is at
> least, say, 20 pages, , it should have a separate FDL permission
> notice and copy of the FDL.

I don't think gdbint can be efficiently used without the user manual.

> As to the GPL - that is a political and authorial decision - is it
> useful practically and/or politically to give people a copy of the GPL
> in the manual?  I think RMS has said in the past that he thinks the
> major GNU manuals should include a copy.  Ask him if you want, but it
> is probably a good idea.  Not required by license, but a good idea.

Yes, I agree.