All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Anand Kumria" <wildfire@progsoc.org>
To: netdev@vger.kernel.org
Subject: Re: [RFC] [PATCH 1/3] adds iso3166-1 support
Date: Wed, 25 Oct 2006 01:44:52 +0000 (UTC)	[thread overview]
Message-ID: <ehmfij$99h$1@sea.gmane.org> (raw)
In-Reply-To: 43e72e890610231545n389d8a6dy89bb476101953234@mail.gmail.com

On Mon, 23 Oct 2006 18:45:23 -0400, Luis R. Rodriguez wrote:

> iso3166-1
> 
> ISO 3166-1, as part of the ISO 3166 standard, provides codes for the names
> of countries and dependent areas. It was first published in 1974 by
> the International Organization for Standardization (ISO) and defines three
> different codes for each area:

[snip]

+	r |= iso3166_1_add(887, "YE", "YEM", 
+		"Yemen");
+	r |= iso3166_1_add(891, "CS", "SCG", 
+		"Serbia and Montenegro");
+	r |= iso3166_1_add(894, "ZM", "ZMB", 
+		"Zambia");


According to the ISO, at:

<http://www.iso.org/iso/en/commcentre/pressreleases/2006/Ref1031.html>

and

<http://www.iso.org/iso/en/prods-services/iso3166ma/03updates-on-iso-3166/nlv12-div.html>

Serbia and Montenegro have been allocated new codes, RS and ME respectively.

Is this ISO3166 stuff supposed to track the standard? If so, what happens when a country splits or two join together?

Will that require lock-step updates to user-space, or will it be insulated byt this changes?

Regards,
Anand


  parent reply	other threads:[~2006-10-25  1:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-23 22:45 [RFC] [PATCH 1/3] adds iso3166-1 support Luis R. Rodriguez
2006-10-24  8:30 ` Johannes Berg
2006-10-24 15:59   ` Luis R. Rodriguez
2006-10-24 16:08     ` Johannes Berg
2006-10-25 15:05       ` Luis R. Rodriguez
2006-10-25  1:44 ` Anand Kumria [this message]
2006-10-25 15:09   ` Luis R. Rodriguez

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='ehmfij$99h$1@sea.gmane.org' \
    --to=wildfire@progsoc.org \
    --cc=netdev@vger.kernel.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.