Get work in the healthcare field now

Start studying today.





------------------------------------------------------------------------------------------------------------------------ On 06/30/2009 12:12 PM, supp ... @bapfish.org.uk wrote: I have now reverted to Tb 2.0.0.21 and the problem persists. I restored a MozBackup prior to the problem and it was OK (eg. it didn't show multiple email addresses in the 'from' address menu) As the backup was too old to be of use I have reverted back to the latest backup where the problem returned again. Does it have same account information as you current profile has, i.e, did you make any changes in account structure ( like added a new account or removed any existing account ) after taking that account? If no then you can use your latest profile but just replace it's prefs.js file with backed up prefs.js file. There have been both further identities and an extra account since the old backup, so not possible. Looking at the problem prefs.js file, identities only show once and it seems to look OK. I can reproduce same problem if i modify the value of this preference mail.account.account.identities for example, if i change mail.account.account2.identities id1,id3,id4,id5 to mail.account.account2.identities id1,id3,id4,id5,id1,id3,id4,id5 'From' drop-down in compose window will display duplicate identities. I'm sure what happened in your case. Do you see any very long line in your _problematic_ prefs.js file? Looking at my problematic prefs.js file I only see an ordinary to be expected mail.account.account2.identities line It says: mail.account.account2.identities id1,id2,id3,id4 (eg. correct number of ids) There is a very long line starting: mail.accountmanager.accounts account1(x11),account2,account1(x9),account2,account1(x4),account2, account3,account4,account1(x4),account2,account3,account4,account3, account4,account3,account4 eg. account1(x4) = account1,account1,account1,account1 Is this line OK? -- Bernard - supp ... @bapfish.org.uk _______________________________________________ support -thunderbird mailing list supp ... @lists.mozilla.org https://lists.mozilla.org/listinfo/support-thunderbird To unsubscribe, send an email to supp ... @lists.mozilla.org ?subject=unsubscribe A release candidate GIT 1.6.3.rc0 is available at the usual places for testing: http://www.kernel.org/pub/software/scm/git/ git-1.6.3.rc0.tar.{gz,bz2} (source tarball) git-htmldocs-1.6.3.rc0.tar.{gz,bz2} (preformatted docs) git-manpages-1.6.3.rc0.tar.{gz,bz2} (preformatted docs) The RPM binary packages for a few architectures are found in: testing/git-*-1.6.3.rc0-1.fc9.$arch.rpm (RPM) ---------------------------------------------------------------- GIT v1.6.3 Release Notes (draft) ================================ With the next major release, "git push" into a branch that is currently checked out will be refused by default. You can choose what should happen upon such a push by setting the configuration variable receive.denyCurrentBranch in the receiving repository. To ease the transition plan, the receiving repository of such a push running this release will issue a big warning when the configuration variable is missing. Please refer to: http://git.or.cz/gitwiki/GitFaq#non-bare http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007 for more details on the reason why this change is needed and the transition plan. For a similar reason, "git push $there :$killed" to delete the branch $killed in a remote repository $there, if $killed branch is the current branch pointed at by its HEAD, gets a large warning. You can choose what should happen upon such a push by setting the configuration variable receive.denyDeleteCurrent in the receiving repository. When the user does not tell "git push" what to push, it has always pushed matching refs. For some people it is unexpected, and a new configuration variable push.default has been introduced to allow changing a different default behaviour. To advertise the new feature, a big warning is issued if this is not configured and a git push without arguments is attempted. Updates since v1.6.2 -------------------- (subsystems) * various git-svn updates. (performance) * many uses of lstat(2) in the codepath for "git checkout" have been optimized out. * pruning reflog entries that are unreachable from the tip of the ref during "git reflog prune" (hence "git gc") was very inefficient. (usability, bells and whistles ) * rsync:/path/to/repo can be used to run git over rsync for local repositories. It may not be useful in practice; meant primarily for testing. * http transport learned to prompt and use password when fetching from or pushing to http://user @host.xz/ URL. * (msysgit) progress output that is sent over the sideband protocol can be handled appropriately in Windows console. * "--pretty=