Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
P
puri
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
1
Issues
1
List
Boards
Labels
Service Desk
Milestones
Merge Requests
1
Merge Requests
1
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
clpm
puri
Commits
96bbcefd
Commit
96bbcefd
authored
Mar 17, 2004
by
Kevin M. Rosenberg
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
r8757: Automated commit for Debian build of puri upstream-version-1.3.1.1
parent
d4af34af
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
8 additions
and
1 deletion
+8
-1
debian/changelog
debian/changelog
+6
-0
debian/control
debian/control
+1
-1
src.lisp
src.lisp
+1
-0
No files found.
debian/changelog
View file @
96bbcefd
cl-puri (1.3.1.1-1) unstable; urgency=low
* Use #:net.uri nickname on non-Allegro platforms
-- Kevin M. Rosenberg <kmr@debian.org> Tue, 16 Mar 2004 18:32:10 -0700
cl-puri (1.3.1-1) unstable; urgency=low
* New upstream
...
...
debian/control
View file @
96bbcefd
...
...
@@ -3,7 +3,7 @@ Section: devel
Priority: optional
Maintainer: Kevin M. Rosenberg <kmr@debian.org>
Build-Depends-Indep: debhelper (>= 4.0.0)
Standards-Version: 3.6.0
Standards-Version: 3.6.
1.
0
Package: cl-puri
Architecture: all
...
...
src.lisp
View file @
96bbcefd
...
...
@@ -26,6 +26,7 @@
(
defpackage
#:puri
(
:use
#:cl
)
#-
allegro
(
:nicknames
#:net.uri
)
(
:export
#:uri
; the type and a function
#:uri-p
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment