From: Giorgos Keramidas <keramida@ceid.upatras.gr>
To: Katsumi Yamaoka <yamaoka@jpl.org>,
rms@gnu.org, juri@jurta.org, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Splitting gnus.texi
Date: Sun, 30 Sep 2007 23:50:32 +0300 [thread overview]
Message-ID: <20070930205032.GA11749@kobe.laptop> (raw)
In-Reply-To: <v9y7euq7sb.fsf@marauder.physik.uni-ulm.de>
On 2007-09-26 08:07, Reiner Steib <reinersteib+gmane@imap.cc> wrote:
>On Wed, Sep 26 2007, Katsumi Yamaoka wrote:
>>>>>>> Richard Stallman wrote:
>>
>>> It would be good to split gnus.texi into 10 to 15 files
>>> just because it is so big. Similar for calc.texi.
>>
>> At least for gnus.texi, I don't see the benefit of splitting.
>> It's indeed big, but is not too big to edit with Emacs. Rather,
>> I cannot ignore a disadvantage of splitting it. I sometimes
>> write in it. Since various Gnus functions are related mutually,
>> I frequently check other items concerned when I write something.
>> [...] But if gnus.texi is split into 10 to 15 files, it will be
>> quite troublesome.
>>
>> I can agree with splitting if it is very useful to users, though.
>
> Additionally, splitting destroys CVS annovate (vc-annotoate). I also
> see no problem with the size.
This doesn't have to be the result of splitting. The files may be
'repo-copied' by one of the CVS admins, creating let's say 3 files:
gnus.texi
gnus-news.texi
gnus-email.texi
These files can then be 'trimmed' with a normal commit, and the trimmed
text becomes a changeset of its own. This way 'cvs annotate' will still
show useful information.
next prev parent reply other threads:[~2007-09-30 20:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1IPj9V-0003Yo-MM@fencepost.gnu.org>
[not found] ` <mxejhjdrqs.fsf@fencepost.gnu.org>
[not found] ` <E1IRYNh-0003dG-Sc@fencepost.gnu.org>
[not found] ` <jer6lh2f4e.fsf@sykes.suse.de>
[not found] ` <E1ISGc3-000624-G9@fencepost.gnu.org>
[not found] ` <izlkbnk2us.fsf@fencepost.gnu.org>
[not found] ` <87fy1v36be.fsf@neutrino.caeruleus.net>
[not found] ` <u3axvv8rp.fsf@gnu.org>
[not found] ` <E1ISbWd-00074O-HB@fencepost.gnu.org>
[not found] ` <87fy1ut4hp.fsf@jurta.org>
2007-09-24 17:10 ` Splitting gnus.texi (was: Split man directory) Reiner Steib
2007-09-25 10:44 ` Richard Stallman
2007-09-26 0:23 ` Splitting gnus.texi Katsumi Yamaoka
2007-09-26 6:07 ` Reiner Steib
2007-09-30 20:50 ` Giorgos Keramidas [this message]
2007-09-30 21:34 ` Reiner Steib
2007-09-30 21:46 ` Giorgos Keramidas
2007-09-26 8:55 ` Juri Linkov
2007-09-26 18:14 ` Directory doc/gnus in Emacs CVS (was: Splitting gnus.texi) Reiner Steib
2007-10-20 22:33 ` Directory doc/gnus in Emacs CVS Bill Wohler
2007-10-21 9:37 ` Reiner Steib
2007-10-21 16:26 ` Richard Stallman
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=20070930205032.GA11749@kobe.laptop \
--to=keramida@ceid.upatras.gr \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=rms@gnu.org \
--cc=yamaoka@jpl.org \
/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;
as well as URLs for NNTP newsgroup(s).