[Pkg-isocodes-devel] Document how we monitor changes to "upstream"?
Tobias Quathamer
toddy at debian.org
Tue Apr 14 14:08:33 UTC 2009
- Previous message: [Pkg-isocodes-devel] [SCM] ISO language, territory, currency, script codes and their translations branch, master, updated. iso-codes/3.8-41-g8304446
- Next message: [Pkg-isocodes-devel] [SCM] ISO language, territory, currency, script codes and their translations branch, master, updated. iso-codes/3.8-42-g53dc086
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
On Tuesday 27 January 2009 20:13:11 Alexis Darrasse wrote:
> On Tue, Jan 27, 2009 at 07:38:47PM +0100, Christian Perrier wrote:
> > Currently, we have no reference about the way we all try to catch up
> > with "upstream changes.
> >
> > I suggest we document this in the README.
>
> Excellent idea.
Done, great idea indeed.
Regards,
Tobias
--
Tobias Quathamer | There are two rules for success:
Hamburg, Germany | 1. Never tell everything you know.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-isocodes-devel/attachments/20090414/23dbba10/attachment.pgp>
- Previous message: [Pkg-isocodes-devel] [SCM] ISO language, territory, currency, script codes and their translations branch, master, updated. iso-codes/3.8-41-g8304446
- Next message: [Pkg-isocodes-devel] [SCM] ISO language, territory, currency, script codes and their translations branch, master, updated. iso-codes/3.8-42-g53dc086
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the Pkg-isocodes-devel
mailing list