head	1.1;
branch	1.1.1;
access;
symbols
	netbsd-11-0-RC5:1.1.1.1
	netbsd-11-0-RC4:1.1.1.1
	netbsd-11-0-RC3:1.1.1.1
	netbsd-11-0-RC2:1.1.1.1
	netbsd-11-0-RC1:1.1.1.1
	perseant-exfatfs-base-20250801:1.1.1.1
	netbsd-11:1.1.1.1.0.4
	netbsd-11-base:1.1.1.1
	perseant-exfatfs-base-20240630:1.1.1.1
	perseant-exfatfs:1.1.1.1.0.2
	perseant-exfatfs-base:1.1.1.1
	isl-0-26:1.1.1.1
	isl:1.1.1;
locks; strict;
comment	@# @;


1.1
date	2023.12.29.22.07.41;	author mrg;	state Exp;
branches
	1.1.1.1;
next	;
commitid	8dpf9JCshBX4tpSE;

1.1.1.1
date	2023.12.29.22.07.41;	author mrg;	state Exp;
branches;
next	;
commitid	8dpf9JCshBX4tpSE;


desc
@@



1.1
log
@Initial revision
@
text
@[Mostly copied from git's SubmittingPatches]

	Commits:

	- make commits of logical units
	- check for unnecessary whitespace with "git diff --check"
	  before committing
	- do not check in commented out code or unneeded files
	- the first line of the commit message should be a short
	  description and should skip the full stop
	- the body should provide a meaningful commit message, which
	  includes motivation for the change, and contrasts
	  its implementation with previous behaviour
	- the lines of this body should have at most 76 columns
	- if you want your work included in isl.git, add a
	  "Signed-off-by: Your Name <you@@example.com>" line to the
	  commit message (or just use the option "-s" when
	  committing) to confirm that you agree to the Developer's
	  Certificate of Origin
	- make sure that you have tests for the bug you are fixing
	- make sure that the test suite passes after your commit

	Patch:

	- use "git format-patch -M" to create the patch
	- do not PGP sign your patch
	- send a single patch per mail, e.g., using git-send-email(1)
	- do not attach your patch, but read in the mail
	  body, unless you cannot teach your mailer to
	  leave the formatting of the patch alone.
	- be careful doing cut & paste into your mailer, not to
	  corrupt whitespaces.
	- provide additional information (which is unsuitable for
	  the commit message) between the "---" and the diffstat
	- if you change, add, or remove a command line option or
	  make some other user interface change, the associated
	  documentation should be updated as well.
	- if your name is not writable in ASCII, make sure that
	  you send off a message in the correct encoding.
	- send the patch to the development mailing list
	  (isl-development@@googlegroups.com).  If you use
	  git-send-email(1), please test it first by sending email
	  to yourself.

	Revisions:

	- add the revision number inside square brackets to
	  the subject line (e.g., use --subject-prefix='PATCH v2'
	  when creating the patch)
	- recall the major issues discovered during the previous
	  review and explain how you addressed them or why you
	  disagree.  Do so either in a cover letter, between the
	  "---" and the diffstat or in a separate message.
@


1.1.1.1
log
@initial import of isl 0.26.

this enables additional optimisations in GCC.  from the README:

isl is a thread-safe C library for manipulating sets and relations
of integer points bounded by affine constraints.  The descriptions of
the sets and relations may involve both parameters and existentially
quantified variables.  All computations are performed in exact integer
arithmetic using GMP.

isl is released under the MIT license, but depends on the LGPL GMP
library.
@
text
@@