Gnus development mailing list
 help / color / mirror / Atom feed
From: Julien Cubizolles <j.cubizolles@free.fr>
To: Erik Colson <eco@ecocode.net>
Cc: ding@gnus.org
Subject: Re: A command to break threads
Date: Sat, 21 Nov 2015 13:55:23 +0100	[thread overview]
Message-ID: <8737vz4imc.fsf@free.fr> (raw)
In-Reply-To: <m2si3z8slw.fsf@ecocode.net> (Erik Colson's message of "Sat, 21 Nov 2015 13:06:03 +0100")

Erik Colson <eco@ecocode.net> writes:

> Julien Cubizolles <j.cubizolles@free.fr> writes:
>
>> If I'm not mistaken, gnus-summary-reparent-thread and
>> gnus-summary-reparent-children don't allow it since they only move
>> messages to make them children of a parent message already existing.
>
> you can edit the message and remove the "references" header.

Thank you, that's what I've been doing. Don't you think it would be a
nice to have gnus-summary-reparent-thread do it, with a C-u prefix for
instance ?

Julien.



      reply	other threads:[~2015-11-21 12:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-21 11:32 Julien Cubizolles
2015-11-21 12:06 ` Erik Colson
2015-11-21 12:55   ` Julien Cubizolles [this message]

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=8737vz4imc.fsf@free.fr \
    --to=j.cubizolles@free.fr \
    --cc=ding@gnus.org \
    --cc=eco@ecocode.net \
    /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).