| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
PR: ports/82579
Submitted by: Radim Kolar <hsn@netmag.cz>
Approved by: maintainer timeout (3 weeks)
Notes:
svn path=/head/; revision=139341
|
|
|
|
|
|
|
|
| |
PR: ports/68775 [1]
Submitted by: Radim Kolar <hsn@netmag.cz>
Notes:
svn path=/head/; revision=117769
|
|
|
|
|
|
|
|
|
|
| |
signed archive.
PR: ports/64493
Submitted by: Sebastian Klemke
Notes:
svn path=/head/; revision=112266
|
|
|
|
|
|
|
|
| |
PR: ports/65754
Submitted by: Frank Ruell <stoerte@dreamwarrior.net>
Notes:
svn path=/head/; revision=108042
|
|
|
|
|
|
|
|
|
| |
building and running tla.
Suggested by: tobez
Notes:
svn path=/head/; revision=102684
|
|
|
|
|
|
|
|
|
|
| |
- SIZEify it
- added master sites (with conversion to main GNU site)
- use ${PRINTF}
- corrected WWW: in pkg-descr.
Notes:
svn path=/head/; revision=102290
|
|
|
|
|
|
|
| |
(Part 2)
Notes:
svn path=/head/; revision=99920
|
|
|
|
|
|
|
|
|
|
|
|
| |
script. Shut down a portlint warning too.
Committed because I did the previous update.
PR: ports/60820
Submitted by: Olivier Tharan <olive@oban.frmug.org>
Notes:
svn path=/head/; revision=97090
|
|
|
|
|
|
|
| |
OK'd by: seanc (MAINTAINER)
Notes:
svn path=/head/; revision=96484
|
|
|
|
| |
Notes:
svn path=/head/; revision=93890
|
|
|
|
|
|
|
| |
Submitted by: roberto
Notes:
svn path=/head/; revision=91098
|
|
|
|
|
|
|
|
| |
Submitted by: Curtis.Dunham@alltel.com
Obtained from: arch-users mailing list
Notes:
svn path=/head/; revision=87752
|
|
Arch is a really nifty revision control system. It's "whole-tree
changeset based" which means, roughly, that it can handle (with atomic
commits) file and directory adds, deletes, and renames cleanly, and
that it does branching simply and easily. Arch is also "distributed"
which means, for example that you can make arch branches of your own
from remote projects, even if you don't have write access to the
revision control archives for those projects.
This looks to be as close to an open source p4 replacement as one could
hope without being p4. I'll go so far as to suggest that if this SCM
was employed by the BSD crowd, merging changes between dragonfly (post
source repo reorog), NetBSD, and OpenBSD would be radically less painful.
It is very possible that the dragonfly fork may not have happened under
the arch SCM development methodology, but if it did, at the very least it
would be possible to incorporate dillion's reorg work in a single patch
set, no cvs admin repo surgery needed.
WWW: http://arch.fifthvision.net/bin/view
Notes:
svn path=/head/; revision=87145
|