Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Merciadri Luca <Luca.Merciadri@student.ulg.ac.be>
To: info-gnus-english@gnu.org
Subject: Re: Follow-Ups and multiple groups?
Date: Fri, 07 May 2010 23:20:16 +0200	[thread overview]
Message-ID: <878w7vxvcf.fsf@merciadriluca-station.MERCIADRILUCA> (raw)
In-Reply-To: <87pr17bmxy.fsf@topper.koldfront.dk>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

asjo@koldfront.dk (Adam Sjøgren) writes:

> On Fri, 07 May 2010 18:03:52 +0200, Merciadri wrote:
>
>> I then use `Newsgroups: ' and type `hiearchy.group1,hiearchy.group2'
>
>> * Why is Gnus repeatedly asking me if there are any follow-ups to my
>> * message? What are these?
>
> Gnus is asking you what group to put in the Followup-To header, which
> allows you to indicate in which of the groups you are posting to the
> discussion (any followups) should be directed to.
Okay. But giving nothing for followups should not prevent Gnus from
sending the article to the precited groups, should it?

> Crossposting is often not a good idea.
I know, but this was really justified here. (If it was not, I would
not have even tried it.)

>> * Is my way to specify the different posting groups (i.e. with a
>> * comma) correct? When trying to post to multiple groups, it never
>> * works, but when I use only one group, it works. Why?
>
> What do you mean "it never works"? Descrive what happens...
What happens is simple: an article (/thread) is never created in any
of the two groups that I specified in `Newsgroups'. But if I
individually send the article to each group, it appears in both
groups.

Why? Thanks.
- -- 
Merciadri Luca
See http://www.student.montefiore.ulg.ac.be/~merciadri/
- -- 

Liberty without learning is always in peril; learning without liberty
 is always in vain. (John F. Kennedy)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iEYEARECAAYFAkvkhBAACgkQM0LLzLt8MhxsBwCfQc1FQksQ+a06i5p69DE+YryG
1QkAoKAHZxV1SghmcmTfaZeGarDRmqiJ
=TNo3
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2010-05-07 21:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07 16:03 Merciadri Luca
2010-05-07 18:12 ` Adam Sjøgren
2010-05-07 18:18   ` Adam Sjøgren
2010-05-07 21:20     ` Merciadri Luca
2010-05-07 21:20   ` Merciadri Luca [this message]
2010-05-07 21:45     ` Adam Sjøgren
2010-05-08 13:12       ` Merciadri Luca
2010-05-08 13:16       ` Merciadri Luca
2010-05-08 13:52         ` Adam Sjøgren
2010-05-09 12:12         ` Merciadri Luca
2010-05-08 13:16       ` Merciadri Luca
2010-05-08 13:20       ` Merciadri Luca
2010-05-08 13:24         ` Merciadri Luca
2010-05-08 13:59         ` Adam Sjøgren
2010-05-08 20:11           ` Merciadri Luca
2010-05-08 20:34             ` Adam Sjøgren
2010-05-08 21:27               ` Merciadri Luca
2010-05-09 17:50                 ` José Manuel García-Patos
2010-05-09 18:51                   ` Merciadri Luca

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=878w7vxvcf.fsf@merciadriluca-station.MERCIADRILUCA \
    --to=luca.merciadri@student.ulg.ac.be \
    --cc=info-gnus-english@gnu.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).