Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: bm@bjornmichelsen.com (=?UNKNOWN?Q?Bj=C3=B8rn?= Michelsen)
Subject: [sup-talk] Saving status of merged threads with '#' on next branch
Date: Wed, 08 Apr 2009 22:44:34 +0200	[thread overview]
Message-ID: <1239177702-sup-8165@snowstorm> (raw)

Hi all,

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'm currently running sup from the next branch. But, I also checked the
command on the 0.7 gem version without any luck.

I'm a bit lost as to where I should begin troubleshooting, so I'm
wondering if someone else have had the same problem?

Maybe I have misinterpreted the command?
-- 
Mvh.
Bj?rn Michelsen
MOB: +47 934 55 474


             reply	other threads:[~2009-04-08 20:44 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 [this message]
2009-04-09 15:39 ` Mark Alexander
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=1239177702-sup-8165@snowstorm \
    --to=bm@bjornmichelsen.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