[PATCH] Mention subscriptions via Server buffer at Subscription Commands (was: when one has a list of 35 groups one wants to subscribe to)

[Tassilo Horn <tassilo@member.fsf.org>]

	* gnus.texi (Subscription Commands): Mention that you can also
	subscribe to new groups via the Server buffer, which is probably more
	convenient when subscribing to many groups.
---
 texi/ChangeLog |    6 ++++++
 texi/gnus.texi |    6 ++++++
 2 files changed, 12 insertions(+), 0 deletions(-)

diff --git a/texi/ChangeLog b/texi/ChangeLog
index a5246c9..353e8a7 100644
--- a/texi/ChangeLog
+++ b/texi/ChangeLog
@@ -1,3 +1,9 @@
+2010-10-22  Tassilo Horn  <tassilo@member.fsf.org>
+
+	* gnus.texi (Subscription Commands): Mention that you can also
+	subscribe to new groups via the Server buffer, which is probably more
+	convenient when subscribing to many groups.
+
 2010-10-21  Julien Danjou  <julien@danjou.info>
 
 	* message.texi (Message Headers): Allow message-default-headers to be a
diff --git a/texi/gnus.texi b/texi/gnus.texi
index 95ae10a..882c384 100644
--- a/texi/gnus.texi
+++ b/texi/gnus.texi
@@ -2211,6 +2211,12 @@ selected.
 @section Subscription Commands
 @cindex subscription
 
+The following commands allow for managing your subscriptions in the
+Group buffer.  If you want to subscribe to many groups, it's probably
+more convenient to go to the @ref{Server Buffer}, and choose the
+server there using @kbd{RET} or @kbd{SPC}.  Then you'll have the
+commands listed in @ref{Browse Foreign Server} at hand.
+
 @table @kbd
 
 @item S t
-- 
1.7.3.1

Tassilo Horn <tassilo@member.fsf.org> writes:

> When I want to subscribe to many groups, I enter that server via the
> *Server* buffer so that I can see the complete group listing and use
> isearch to find my groups.  So I guess, a link to the server buffer
> would be a good thing to have in that section.  (I'll add one...)

Ok, I've tried to add one.  If it seems ok, could someone please commit
it for me?  (Since Gnus switched from CVS to git, I think I've lost my
credentials...)

BTW: Is that the right way to send patches made with "git format-patch"?
I think Carsten Dominik (org-mode author) once told me that the patch
has to come first in the mail so that it can be applied more easily from
inside mail clients, because then one could pipe the complete mail to
git.  I guess with Gnus, you don't have that restriction and only pipe
the patch, no matter where it is, right?

Bye,
Tassilo