Re: [PATCH] use natural ordering to display list of branches.

["Mike Ralphson" <mike.ralphson@gmail.com>]

2008/6/5 Cedric Vivier <cedricv@neonux.com>:
>
> This small patch makes git display list of branches in natural order.
> This way, when you name your branches against, for instance, a bug number from
> some bug-tracking tool, the list will show up in a natural/human/logical order.

[Included as part of patch:]

> +
> +  strnatcmp.c -- Perform 'natural order' comparisons of strings in C.
> +  Copyright (C) 2000, 2004 by Martin Pool <mbp sourcefrog net>
> +
> +  This software is provided 'as-is', without any express or implied
> +  warranty.  In no event will the authors be held liable for any damages
> +  arising from the use of this software.
> +
> +  Permission is granted to anyone to use this software for any purpose,
> +  including commercial applications, and to alter it and redistribute it
> +  freely, subject to the following restrictions:
> +
> +  1. The origin of this software must not be misrepresented; you must not
> +     claim that you wrote the original software. If you use this software
> +     in a product, an acknowledgment in the product documentation would be
> +     appreciated but is not required.
> +  2. Altered source versions must be plainly marked as such, and must not be
> +     misrepresented as being the original software.
> +  3. This notice may not be removed or altered from any source distribution.

2008/6/5 Junio C Hamano <gitster@pobox.com>:
> Perhaps, as long as we somehow mark clearly the new files added with this
> patch as "borrowed code" and not part of git proper...
>...
>
> What the big license notice comment at the top says sounded Ok to me as
> well.

IANAL, but I'm not 100% sure clauses 2a or 3 are strictly GPL
compatible (especially as "altered from" is unlikely to be interpreted
in only one way).

Perhaps we can ask the original author (cc'd) if he is prepared to
license it under GPL2?

I also think the license policy for inclusion in git should be spelt
out in the documentation, i.e. GPL (2+), GPL2 only, GPL2 compatible
etc. SubmittingPatches touches on this area, but only in terms of the
DCoO.  README merely states "Git is an Open Source project covered by
the GNU General Public License."

Some c files state GPL v2 only, others v2 with the "any later version" wording.

I had the same issue when the replacement qsort() implementations came up.

As to the patch, I like the intent, but for consistency should it not
also apply to tags?

Mike