for NM service; only emit when state really changes
- Use hash tables correctly so that the key (which was previously owned
by the D-Bus message) now has the same lifetime as the value, since
- the key is now taken from the the NMVPNConnection itself. This
+ the key is now taken from the NMVPNConnection itself. This
really fixes the double-VPN names in the applet
2007-08-13 Dan Williams <dcbw@redhat.com>
/* Handle pseudo groups: profile, active */
if (success && group_profile) {
if (str1->len > 0) {
- g_set_error (error, NMCLI_ERROR, 0, _("'%s' has to be alone'"),
+ g_set_error (error, NMCLI_ERROR, 0, _("'%s' has to be alone"),
CON_SHOW_DETAIL_GROUP_PROFILE);
success = FALSE;
} else
}
if (success && group_active) {
if (str2->len > 0) {
- g_set_error (error, NMCLI_ERROR, 0, _("'%s' has to be alone'"),
+ g_set_error (error, NMCLI_ERROR, 0, _("'%s' has to be alone"),
CON_SHOW_DETAIL_GROUP_ACTIVE);
success = FALSE;
} else
case NMC_EDITOR_MAIN_CMD_SAVE:
printf (_("save [persistent|temporary] :: save the connection\n\n"
"Sends the connection profile to NetworkManager that either will save it\n"
- "pesistently, or will only keep it in memory. 'save' without an argument\n"
+ "persistently, or will only keep it in memory. 'save' without an argument\n"
"means 'save persistent'.\n"
"Note that once you save the profile persistently those settings are saved\n"
"across reboot or restart. Subsequent changes can also be temporary or\n"
Update the connection with new settings and properties (replacing
all previous settings and properties) but do not immediately save
the connection to disk. Secrets may be part of the update request
- and may sent to a Secret Agent for storage, depending on the the
+ and may sent to a Secret Agent for storage, depending on the
flags associated with each secret.
Use the 'Save' method to save these changes to disk. Note