public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "kris dot van dot hees at oracle dot com" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/4562] Editing a session name causes a new session to be created Date: Tue, 29 May 2007 19:22:00 -0000 [thread overview] Message-ID: <20070529192206.26173.qmail@sourceware.org> (raw) In-Reply-To: <20070529185302.4562.kris.van.hees@oracle.com> ------- Additional Comments From kris dot van dot hees at oracle dot com 2007-05-29 19:22 ------- Problem is that sessions are stored under their names, so when you change the name of the session using the edit functionality of the druid, and close the druid, it triggers a save of the current session, which causes it to get saved under the new name. The session manager acts as if the session was renamed, but in reality (in the underlying fs representation of sessions) a new one got created. So, when you start frysk again, it now finds both. When you chamge the name, the session under the new name ought to be automatically deleted at the time of saving the session under its new name. You can't really do it prior to the save of the new session information, because a crash or deliberate abort of frysk would leave you without even the old version of the session. -- http://sourceware.org/bugzilla/show_bug.cgi?id=4562 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-05-29 19:22 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-05-29 18:53 [Bug general/4562] New: " kris dot van dot hees at oracle dot com 2007-05-29 19:22 ` kris dot van dot hees at oracle dot com [this message] 2007-06-20 15:15 ` [Bug general/4562] " swagiaal at redhat dot com
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=20070529192206.26173.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=frysk-bugzilla@sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).