Log of /contributions/modules/cvslog/cvs_local.example.inc
Parent Directory
| 
Revision Log
| 
Revision Graph
Revision
1.11 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Tue Mar 3 19:55:58 2009 UTC
(8 months, 3 weeks ago)
by
dww
Branch:
MAIN
Changes since
1.10: +5 -8 lines
Diff to
previous 1.10
#390032 by dww: Fixed a bug where non-admins could no longer edit a
HEAD release node to move the "CVS branch" field to a more specific
branch (e.g. moving a HEAD node called "6.x-1.x-dev" to DRUPAL-6--1).
Revision
1.8 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Tue Dec 4 02:42:06 2007 UTC
(23 months, 3 weeks ago)
by
dww
Branch:
MAIN
Changes since
1.7: +2 -2 lines
Diff to
previous 1.7
#193129 by dww: Fixed bug where DRUPAL-6--1 branches weren't correctly
associated with 6.x-1.x-dev releases due to code that was handling the
evil DRUPAL-5 special case. Now, the special case only fires if the
API version is less than 6.
Revision
1.1.2.16 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Thu Aug 16 18:07:25 2007 UTC
(2 years, 3 months ago)
by
dww
Branch:
DRUPAL-4-7--2
CVS Tags:
DRUPAL-4-7--2-2
Changes since
1.1.2.15: +4 -4 lines
Diff to
previous 1.1.2.15
, to
branch point 1.1
#91195 by dww: Fixed bug where cvs_get_version_from_tag() was assumed
to exist, but was only implemented in cvs_local.inc. Now, the function
is defined in cvs.module, but if cvs_local_get_tag_from_version()
exists (from cvs_local.inc), that implementation is used, instead.
The same fix has also been made for cvs_get_tag_from_version().
Revision
1.6 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Thu Aug 16 18:07:08 2007 UTC
(2 years, 3 months ago)
by
dww
Branch:
MAIN
CVS Tags:
DRUPAL-5--1-0
Changes since
1.5: +4 -4 lines
Diff to
previous 1.5
#91195 by dww: Fixed bug where cvs_get_version_from_tag() was assumed
to exist, but was only implemented in cvs_local.inc. Now, the function
is defined in cvs.module, but if cvs_local_get_tag_from_version()
exists (from cvs_local.inc), that implementation is used, instead.
The same fix has also been made for cvs_get_tag_from_version().
Revision
1.1.2.15 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Mar 21 22:03:13 2007 UTC
(2 years, 8 months ago)
by
dww
Branch:
DRUPAL-4-7--2
Changes since
1.1.2.14: +47 -2 lines
Diff to
previous 1.1.2.14
, to
branch point 1.1
#89699: make release node form smarter when editing HEAD releases (part 1):
now, when a release owner (even a non-admin) is editing a HEAD release
node, if there's another CVS branch that a) matches the same version
info as is currently contained in the release node and b) isn't
already in use, that branch will be a valid choice for the CVS branch
drop-down, so users can move the HEAD release to point to the other
branch. For example, if they had HEAD pointing to "5.x-2.x-dev", and
then they made a DRUPAL-5--2 branch, they could just move the HEAD
release node to point to the new branch, and then make a new HEAD node
for "6.x-1.x-dev" or "5.x-3.x-dev" or whatever they wanted.
Revision
1.5 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Mar 21 22:03:07 2007 UTC
(2 years, 8 months ago)
by
dww
Branch:
MAIN
Changes since
1.4: +47 -2 lines
Diff to
previous 1.4
#89699: make release node form smarter when editing HEAD releases (part 1):
now, when a release owner (even a non-admin) is editing a HEAD release
node, if there's another CVS branch that a) matches the same version
info as is currently contained in the release node and b) isn't
already in use, that branch will be a valid choice for the CVS branch
drop-down, so users can move the HEAD release to point to the other
branch. For example, if they had HEAD pointing to "5.x-2.x-dev", and
then they made a DRUPAL-5--2 branch, they could just move the HEAD
release node to point to the new branch, and then make a new HEAD node
for "6.x-1.x-dev" or "5.x-3.x-dev" or whatever they wanted.
Revision
1.4 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Fri Dec 22 23:55:29 2006 UTC
(2 years, 11 months ago)
by
dww
Branch:
MAIN
Changes since
1.3: +7 -7 lines
Diff to
previous 1.3
#101150 by AjK and dww: port to 5.x API. Still needs more testing and
reviews, but committing to HEAD to ease testing and deployment.
Revision
1.3 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Tue Dec 5 21:52:41 2006 UTC
(2 years, 11 months ago)
by
dww
Branch:
MAIN
Changes since
1.2: +2 -2 lines
Diff to
previous 1.2
merging DRUPAL-4-7--2 branch as tagged at DRUPAL-4-7--2-1 into HEAD:
#97031, #97128, #97735, #97789, #101034, #101170, #101174, #101335, #101338
Revision
1.2 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sun Nov 12 07:36:56 2006 UTC
(3 years ago)
by
dww
Branch:
MAIN
Changes since
1.1: +170 -0 lines
Diff to
previous 1.1
merging DRUPAL-4-7--2 branch as tagged at DRUPAL-4-7--2-0 into HEAD
(#94000: the entire diff for the new release system)
Revision
1.1.2.10 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Oct 25 10:44:26 2006 UTC
(3 years, 1 month ago)
by
dww
Branch:
DRUPAL-4-7--2
Changes since
1.1.2.9: +4 -3 lines
Diff to
previous 1.1.2.9
, to
branch point 1.1
#84706: port cvs.module to releases-as-nodes (also #58066, #75053, #83339)
we want the default stable branch for any version of core to be the
-1.* series, not the -0.* series. for example, DRUPAL-4-7 should give
you the "4.7.x-1.*" releases.
Revision
1.1.2.9 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Oct 25 09:15:32 2006 UTC
(3 years, 1 month ago)
by
dww
Branch:
DRUPAL-4-7--2
Changes since
1.1.2.8: +10 -13 lines
Diff to
previous 1.1.2.8
, to
branch point 1.1
#84706: port cvs.module to releases-as-nodes (also #58066, #75053, #83339)
cvs_release_node.patch_17.txt:
the FAPI crap for trying to set defaults for major, patch and extra
when we're adding a release from "HEAD" is just not working right,
chx/eaton aren't around, and i don't care enough to spend infinite
time on this. so, i ripped out the defaults, and just added a
site-specific description for the fieldset when you're adding/editing
a release pointing at HEAD. that's good enough for now...
Revision
1.1.2.8 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Oct 25 09:13:50 2006 UTC
(3 years, 1 month ago)
by
dww
Branch:
DRUPAL-4-7--2
Changes since
1.1.2.7: +24 -18 lines
Diff to
previous 1.1.2.7
, to
branch point 1.1
#84706: port cvs.module to releases-as-nodes (also #58066, #75053, #83339)
cvs_release_node.patch_16.txt:
- always set the api compatibility taxonomy term, even for core releases.
- initial bugfix for cvs_local_alter_project_release_form(), which is
trying to add site-specific default values for major, patch, and
extra. we now only attempt to add a default if there's not already
one there. however, this is still a little buggy, and things get
saved with a "dev" as the extra, even if you clear it out yourself. :(
Revision
1.1.2.7 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Oct 25 09:09:06 2006 UTC
(3 years, 1 month ago)
by
dww
Branch:
DRUPAL-4-7--2
Changes since
1.1.2.6: +9 -2 lines
Diff to
previous 1.1.2.6
, to
branch point 1.1
#84706: port cvs.module to releases-as-nodes (also #58066, #75053, #83339)
cvs_release_node.patch_14.txt:
update to cvs_local_version_is_valid() that takes advantage of the new
project_release_exists() method from project_release.module, revision
1.1.2.21. this prevents advancing past the version selection page
(only shown if you selected HEAD) if you choose values that would lead
to 2 releases with the same version identification.
Revision
1.1.2.6 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Oct 25 09:01:46 2006 UTC
(3 years, 1 month ago)
by
dww
Branch:
DRUPAL-4-7--2
Changes since
1.1.2.5: +7 -1 lines
Diff to
previous 1.1.2.5
, to
branch point 1.1
#84706: port cvs.module to releases-as-nodes (also #58066, #75053, #83339)
cvs_release_node.patch_11.txt:
- cvs_local.example.inc properly associates tag names to the right
taxonomy term, for both "DRUPAL-4-7*" and "DRUPAL-5*" kinds of tags.
- if the api compatibility is known on page 1 via the tag, when we
land on the final page, the compatibility selector only has that
option and it's selected by default.
Revision
1.1.2.5 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Oct 25 08:59:51 2006 UTC
(3 years, 1 month ago)
by
dww
Branch:
DRUPAL-4-7--2
Changes since
1.1.2.4: +24 -71 lines
Diff to
previous 1.1.2.4
, to
branch point 1.1
#84706: port cvs.module to releases-as-nodes (also #58066, #75053, #83339)
cvs_release_node.patch_10.txt:
big changes for the move to project_release's taxonomy for compatibility:
- remove all references to api_(major|minor)
- add real N-page goodness to the autogenerated taxonomy (if in use).
- once you land on the final page, there's only the selected
compatibility as an option (i.e., you can't change it once you land on
the last page, since the version string has already been determined on
page 2)
- rips out all the crufty, not-really-working api_selector stuff from
the previous patch
Revision
1.1.2.4 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Oct 25 08:56:55 2006 UTC
(3 years, 1 month ago)
by
dww
Branch:
DRUPAL-4-7--2
Changes since
1.1.2.3: +145 -13 lines
Diff to
previous 1.1.2.3
, to
branch point 1.1
#84706: port cvs.module to releases-as-nodes (also #58066, #75053, #83339)
cvs_release_node.patch_9.txt:
- if the user selected 'HEAD' on page 1, page 2 now hides the "API
major" and "API minor" elements, and instead presents a "Drupal core
compatibility" selector with pre-filled values.
- added some more callbacks for local customization
(cvs_local_alter_project_release_form(), cvs_local_version_is_valid(),
and cvs_local_project_release_form_pre_render()).
- fixed a bug in cvs_get_version_from_tag() that screwed up setting the
version_extra field properly based on a cvs tag. also, added a
_cvs_get_extra() method to help with this.
Revision
1.1.2.3 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Oct 25 08:44:56 2006 UTC
(3 years, 1 month ago)
by
dww
Branch:
DRUPAL-4-7--2
Changes since
1.1.2.2: +19 -19 lines
Diff to
previous 1.1.2.2
, to
branch point 1.1
#84706: port cvs.module to releases-as-nodes (also #58066, #75053, #83339)
cvs_release_node.patch_5.txt:
- renamed all occurances of "super" with "API" to be more reasonable
and clear. so, it's now the "API major version", "version_api_major"...
- inside project_release_db_save() if we've got a non-numeric value
for version_patch, just unset it and leave it as a NULL in the DB
(e.g. for "4.7.x-dev" core releases).
Revision
1.1.2.2 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Oct 25 08:38:10 2006 UTC
(3 years, 1 month ago)
by
dww
Branch:
DRUPAL-4-7--2
Changes since
1.1.2.1: +2 -2 lines
Diff to
previous 1.1.2.1
, to
branch point 1.1
#84706: port cvs.module to releases-as-nodes (also #58066, #75053, #83339)
cvs_release_node.patch_3-broken.txt:
1st stab at 2-page form for first selecting the tag, then everything
else, when adding a release.
Revision
1.1.2.1 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Oct 25 08:35:06 2006 UTC
(3 years, 1 month ago)
by
dww
Branch:
DRUPAL-4-7--2
Changes since
1.1: +58 -0 lines
Diff to
previous 1.1
#84706: port cvs.module to releases-as-nodes (also #58066, #75053, #83339)
cvs_release_node.patch_2.txt:
= moves d.o-specific hacks into cvs_local.inc, though the file we'll
ship will be called cvs_local.example.inc so that sites will have to
copy it into place and edit it for their own needs if they want.
= fixed some bugs in cvs_get_version_from_tag():
- need to pass in the $project object for core-specific logic
- have to tell the difference between DRUPAL-4-7 branch and DRUPAL-5-0
release tag
- a little bit more empty() vs. isset() badness dealing with 0 values...
= branches and tags are now sorted nicely and grouped together in the
drop-down when selecting the tag on the release node form.
Revision
1.1
Wed Oct 25 08:35:06 2006 UTC
(3 years, 1 month ago)
by
dww
Branch:
MAIN
Branch point for:
DRUPAL-4-7--2
FILE REMOVED
file cvs_local.example.inc was initially added on branch DRUPAL-4-7--2.
This form allows you to request diffs between any two revisions of this file.
For each of the two "sides" of the diff,
select a symbolic revision name using the selection box, or choose
'Use Text Field' and enter a numeric revision.
