From: marka@pobox.com (Mark Alexander)
Subject: [sup-talk] Saving status of merged threads with '#' on next branch
Date: Thu, 9 Apr 2009 08:39:39 -0700 [thread overview]
Message-ID: <a412e2a70904090839k2b63f3f3v1d63c080902bb7ac@mail.gmail.com> (raw)
In-Reply-To: <1239177702-sup-8165@snowstorm>
2009/4/8 Bj?rn Michelsen <bm at bjornmichelsen.com>:
> For some reason, the '#' command isn't saving the status of tagged
> threads being forced to merge. I get a visual feedback that the threads
> have been put into the same one, but when I come back to the view after
> killing the buffer, they're separated again.
I've noticed this as well. I figured it was a feature, not a bug :-) .
next prev parent reply other threads:[~2009-04-09 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 20:44 =?UNKNOWN?Q?Bj=C3=B8rn?= Michelsen
2009-04-09 15:39 ` Mark Alexander [this message]
2009-04-09 18:02 ` William Morgan
2009-04-15 15:58 ` Bjorn Michelsen
2009-04-15 17:33 ` William Morgan
2009-04-16 9:53 ` Bjorn Michelsen
2009-04-21 13:28 ` William Morgan
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=a412e2a70904090839k2b63f3f3v1d63c080902bb7ac@mail.gmail.com \
--to=marka@pobox.com \
/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