~network-manager/network-manager-vpnc/master : changes

~network-manager/network-manager-vpnc/master » Changes from revision 508

From Revision 493 to 474

Rev	Summary	Authors	Date
493	Update Brazilian Portuguese translation Update Brazilian Portuguese translation	Rafael Fontenelle	7 years ago
492	Updated Danish translation Updated Danish translation	Alan Mortensen	7 years ago
491	shared: reimport shared files shared: reimport shared files Also, change the compiler option to use gnu99 C.	Thomas Haller	7 years ago
490	Update Spanish translation Update Spanish translation	Daniel Mustieles	7 years ago
489	Update German translation Update German translation	Paul Seyfert	7 years ago
488	properties/tests: use different TMPDIR for testing libnm/lib... properties/tests: use different TMPDIR for testing libnm/libnm-glib based tests We compile two versions of the properties tests from the same source file: one for libnm and one for legacy libnm-glib. When running them in parallel with `make -j 4 check`, we must ensure that the tests use different temporary directories. https://bugzilla.gnome.org/show_bug.cgi?id=772471	Thomas Haller	7 years ago
487	Updated Czech translation Updated Czech translation	Zdeněk Hataš	7 years ago
486	Updated Hungarian translation Updated Hungarian translation	Balázs Meskó	7 years ago
485	Updated Polish translation Updated Polish translation	Piotr Drąg	7 years ago
484	Use Unicode in translatable strings Use Unicode in translatable strings See https://developer.gnome.org/hig/stable/typography.html	Piotr Drąg	7 years ago
483	release: bump version to 1.2.5 (development) release: bump version to 1.2.5 (development)	Thomas Haller	7 years ago
482	release: bump version to 1.2.4 release: bump version to 1.2.4	Thomas Haller	7 years ago
481	release: update NEWS release: update NEWS	Thomas Haller	7 years ago
480	Updated German translation Updated German translation	Bernd Homuth	7 years ago
479	build: use m4/compiler_options.m4 from NetworkManager build: use m4/compiler_options.m4 from NetworkManager Copy over the m4 macro from NetworkManager repository, it shall replace m4/compiler_warnings.m4.	Thomas Haller	7 years ago
478	build: use GIT_SHA_RECORD(NM_GIT_SHA) macro from "m4/git-sha... build: use GIT_SHA_RECORD(NM_GIT_SHA) macro from "m4/git-sha-record.m4" See https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=b33aacbc91864f20f4733919af1a4cf8f725ca94	Thomas Haller	7 years ago
477	Updated Spanish translation Updated Spanish translation	Daniel Mustieles	7 years ago
476	Updated Polish translation Updated Polish translation	Piotr Drąg	7 years ago
475	NEWS: update NEWS: update	Thomas Haller	7 years ago
474	all: merge branch 'master' into nm-1-2 all: merge branch 'master' into nm-1-2 With the release of 1.2.0, we branched off 'nm-1-2' branch and bumped the version number on 'master' to 1.3.0. As of today, 'master' still only requires 1.2.0 API of libnm, libnma and NetworkManager. Note that VPN plugins are backward compatible so that it is very much supported to run an older VPN plugin against a newer NM version. That means, there is no reason for maintaining two upstream branches 'master' and 'nm-1-2' that both provide a plugin that has essentially the same requirements w.r.t. the NetworkManager API. Merge 'master' into 'nm-1-2' and rewind the version number from 1.3.0 to 1.2.3. There is now only one maintained branch of the plugin that works with libnm/libnma/NetworkManager >= 1.2.0. This means a user stuck with 1.2 can get the newest features from 'master', instead of a stale 'nm-1-2' branch. Yes, that also means that upstream doesn't provide a bugfix-only branch of 1.2. But then, this is a tiny VPN plugin and not glibc. If a new 1.2.x version has issues it is simply a bug. In this case it's the responsibility of the user/distributor to cherry-pick the fix or revert to a previously working version. This is done to have less work for upstream, but more importantly: it makes clear that 'master' requires only 1.2 NM-API. That is important as improvements are now immediately useable for anybody running NM 1.2.0 or newer. This is contrary to before, where it was strongly implied that 'master' only works with the current development branch of NetworkManager. In other words: this decouples the versioning of the plugin from that of NetworkManager/libnma. The version number 1.2.x now has the meaning or requiring NM API >= 1.2.0. https://bugzilla.gnome.org/show_bug.cgi?id=771013	Thomas Haller	7 years ago

Older »