Log of /contributions/modules/versioncontrol/versioncontrol-backend.inc
Parent Directory
| 
Revision Log
| 
Revision Graph
Revision
1.61 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Fri Oct 16 14:15:26 2009 UTC
(5 weeks, 5 days ago)
by
sdboyer
Branch:
MAIN
CVS Tags:
HEAD
Changes since
1.60: +1 -1104 lines
Diff to
previous 1.60
Merging in work from git by marvil07 for his GSOC project to OO-ify vcsapi. From this commit forward, HEAD is OO.
Revision
1.60 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sun Jun 21 15:33:07 2009 UTC
(5 months ago)
by
jpetso
Branch:
MAIN
Branch point for:
DRUPAL-6--1
Changes since
1.59: +7 -3 lines
Diff to
previous 1.59
Make the "data" column usable by other modules, and migrate more data to it.
This enables us to get rid of the {commit_restrictions} and
{versioncontrol_repository_metadata} tables, whose data is now
stored in $repository['data'] instead.
Requires an update.php run. This commit modifies update 6102 which
I introduced in my previous commit two days ago; if you have already
executed that update then please delete the "data" column from your
{versioncontrol_repositories} table and run it again.
Revision
1.59 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sat Jun 20 09:30:04 2009 UTC
(5 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.58: +4 -2 lines
Diff to
previous 1.58
Introduce a new "data" column for repositories for additional custom properties.
Third-party modules can store data there instead of in separate tables,
which should eventually contribute to the goal of removing the backends'
{versioncontrol_[backend]_repositories} tables.
Also, make the "allow unauthorized commit access" setting per-repository
instead of global, and store it in the new "data" column.
Revision
1.58 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Apr 8 12:58:31 2009 UTC
(7 months, 2 weeks ago)
by
jpetso
Branch:
MAIN
CVS Tags:
DRUPAL-6--1-0-RC1,
DRUPAL-6--1-0-RC2
Changes since
1.57: +47 -15 lines
Diff to
previous 1.57
#426376 by CorniI and jpetso:
New API function versioncontrol_update_operation_labels(),
along with a new hook for reacting to operation label changes.
Good thing that there's finally an API for this - without this code,
backends like Git were required to place queries into Version Control API's
private database tables, and secretly modify stuff that had been publicly
exposed to modules by hook_versioncontrol_operation().
Now there's a sufficiently clean way to do the same thing.
Revision
1.56 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Fri Apr 3 22:06:57 2009 UTC
(7 months, 3 weeks ago)
by
jpetso
Branch:
MAIN
Changes since
1.55: +2 -2 lines
Diff to
previous 1.55
#328035 by Cornil, plus a lot of changes from me:
Make VCS username suggestions and determing username validity pluggable.
Also, fix a bug in the user versioncontrol page that made the passed
repository work incorrectly.
This should make it possible to handle Git & Co. usernames properly.
Revision
1.54 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sun Jan 25 20:37:35 2009 UTC
(10 months ago)
by
jpetso
Branch:
MAIN
CVS Tags:
DRUPAL-6--1-0-BETA1,
DRUPAL-6--1-0-BETA2,
DRUPAL-6--1-0-BETA3,
DRUPAL-6--1-0-BETA4,
DRUPAL-6--1-0-BETA5
Changes since
1.53: +5 -1 lines
Diff to
previous 1.53
Replace lots of
$form['blah'] = array('#type' => 'value', '#value' => $blah);
elements with
$form['#blah'] = $blah;
as the former is now deprecated in Drupal 6.
I hope I didn't miss any form_alter or $form_state['values'] conversions,
anyways I tried to be as thorough as possible.
A few '#type' => 'value' fields are left still, those are the ones that
the form chooses either as fixed value or as selection, depending on the
permissions. No big deal though, I don't feel offended by those :]
Revision
1.53 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sun Jan 25 18:50:43 2009 UTC
(10 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.52: +3 -3 lines
Diff to
previous 1.52
Rename hook_versioncontrol_extract_{repository,account}_data() to
hook_versioncontrol_{repository,account}_submit().
That's consistent with most similar mechanisms known to me in general,
and with Rules' way of doing it in particular.
With this commit, we also get rid of the last instances of $form_values.
Revision
1.52 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sun Jan 25 15:43:23 2009 UTC
(10 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.51: +3 -3 lines
Diff to
previous 1.51
* Port the 5.x workflow_ng integration to 6.x Rules integration.
* Get a drupal_mail()-like $send option into Commit Log's
notification mail functions, and remove 'send' from the function names.
* Bonus feature: new "send notification mail" action for Rules,
and a few more operation properties exposed as event arguments.
Per-user commit subscriptions are now *really* not far away anymore.
Everything involving mails is still untested though,
but despite that I also fixed one bug in the process :)
Revision
1.49 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Mon Jan 5 12:23:59 2009 UTC
(10 months, 2 weeks ago)
by
jpetso
Branch:
MAIN
Changes since
1.48: +23 -61 lines
Diff to
previous 1.48
db_last_insert_id() doesn't work like db_next_id(), as it returns the
previously inserted integer instead of the upcoming one. Instead of
fixing that manually, let's instead have drupal_write_record() do
all the work for us, getting rid of a few more lines of code.
Revision
1.48 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sat Jan 3 13:21:28 2009 UTC
(10 months, 3 weeks ago)
by
jpetso
Branch:
MAIN
Changes since
1.47: +4 -2 lines
Diff to
previous 1.47
D6 upgrade item 3.: New Schema API.
Converted with deadwood, manually tweaked by myself (including table and
column descriptions which have not only been preserved but even extended
and improved). A few todo items are left - converting the 'int' ids to
'serial' in their base tables, and ensuring correct index names for MySQL
and Postgres - but the bulk of database conversion work is probably done.
Revision
1.46.2.8 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Oct 1 12:16:26 2008 UTC
(13 months, 3 weeks ago)
by
jpetso
Branch:
DRUPAL-5--2
Changes since
1.46.2.7: +8 -1 lines
Diff to
previous 1.46.2.7
, to
branch point 1.46
Rejoice! workflow-ng integration. (...which is succeeded by Rules in D6.)
Execute any arbitrary action when a commit/branch/tag operation happens,
optionally filtered by repository, path and label name.
There could certainly be more actions and conditions (and tokens for
mail subject + body provided by Commit Log), but for now it's quite ok.
With a few more additions, this could seriously replace commit_restrictions
with more flexibility and less code, assuming that drupal.org wants to run
Rules (which I find unlikely, so commit_restrictions will probably stay).
Revision
1.46.2.7 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Thu Sep 25 22:26:52 2008 UTC
(14 months ago)
by
jpetso
Branch:
DRUPAL-5--2
Changes since
1.46.2.6: +7 -5 lines
Diff to
previous 1.46.2.6
, to
branch point 1.46
jpetso saves the world *again*!
Here comes the destruction of the Last Difficult Problem that had to be
solved for the Version Control API's 2.x branch. Like, from an API design
point of view. Everything from here on will be a piece of cake,
so to speak. (Of course, there's still lots of work to do.)
Changes? You bet.
- Renamed the versioncontrol_add_whatever() function to
versioncontrol_fetch_whatever(), as the old names just didn't sound
intuitively at all. Especially when introducing
versioncontrol_add_item_revision_id()... NOT.
Everything that loads data into objects (or rather, arrays) and
modifies those rather than returning them as a result is "fetch" now.
Such as the versioncontrol_fetch_item_revision_id() helper function.
- Introduced versioncontrol_fetch_successor_items().
The opposite of versioncontrol_fetch_source_items().
- Major strike #1: Implemented versioncontrol_get_item_history()
in the API module! That means that a) it works for all backends
even if they don't implement on-the-fly file history parsers,
and b) we can assume bearable performance. The current implementation
is the naive one going from item to item, but the potential for large
performance gains is there. Oh, and c) you can limit the number
of returned items. Yay.
- Major strike #2: Got rid of the potential function overkill for
backends to retrieve selected labels. It's now two functions only -
[versioncontrol_backend]_get_selected_label_for_{operation,other_item}() -
and stuffs all the retrievals with related or non-related items
into that "from other item" function. Most important achievement,
keeps the API somewhat usable (although still complex, but that's
probably the price of abstraction and code reuse and stuff).
It struck me during lunch! (...)
- Renamed versioncontrol_get_commits() to versioncontrol_get_commit_operations(),
for consistency.
- Plus, as usual, a few fixes that I already forgot again.
So all the hard API problems are solved, I think. The remaining ones are
either relatively easy or stupid porting work, like for Commit Log.
Ok, so much for saving the world, now on to the boring non-VCS stuff again...
Revision
1.46 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sat Apr 19 13:11:05 2008 UTC
(19 months, 1 week ago)
by
jpetso
Branch:
MAIN
Branch point for:
DRUPAL-5--2
Changes since
1.45: +2 -2 lines
Diff to
previous 1.45
* Extend label restrictions to branch/tag-emulating commits,
and clean up a bit more... the code's a lot nicer to read than yesterday.
* Update copyright headers to 2008.
Revision
1.45 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sat Apr 19 11:16:15 2008 UTC
(19 months, 1 week ago)
by
jpetso
Branch:
MAIN
Changes since
1.44: +5 -5 lines
Diff to
previous 1.44
* Port Commit Restrictions to the new API, and clean it up some more.
* New API functions: versioncontrol_is_{file,directory}_item().
* Plus some other smallish API and documentation fixes/modifications.
Revision
1.44 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Mon Apr 14 11:29:34 2008 UTC
(19 months, 1 week ago)
by
jpetso
Branch:
MAIN
Changes since
1.43: +106 -7 lines
Diff to
previous 1.43
Implement label insertion and item deletion. Plus a few minor fixes.
Those were the last todo items for the "core" of Version Control API,
so let's now track down and adapt all the callers.
Note that, in lack of a backend that's compatible to the updated API,
I couldn't yet test this, so don't expect it to work yet.
Revision
1.42 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Fri Mar 28 15:24:08 2008 UTC
(19 months, 4 weeks ago)
by
jpetso
Branch:
MAIN
Changes since
1.41: +61 -4 lines
Diff to
previous 1.41
Check and if necessary sanitize new items that were passed by VCS backend.
So much for item insertions, next step: label insertions and
deleting items on deleting the repository.
Revision
1.41 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Tue Mar 25 17:49:14 2008 UTC
(20 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.40: +131 -31 lines
Diff to
previous 1.40
Implement inserting operation items - for the largest part, at least.
Not much left before I can head off to port the callers.
Also, fix syntax errors.
Revision
1.40 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Thu Mar 13 21:44:30 2008 UTC
(20 months, 1 week ago)
by
jpetso
Branch:
MAIN
Changes since
1.39: +170 -544 lines
Diff to
previous 1.39
Next step in porting to the new database schema:
Implement loading operation items, and unify the write access and
insertion functions (with the new implementation of inserting items
not done yet). Random porting also in other places.
Have I mentioned that the docs are far more work than the code?
Anyways, it's worth the hassle.
Revision
1.38.2.1 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sun Feb 17 22:59:20 2008 UTC
(21 months, 1 week ago)
by
jpetso
Branch:
DRUPAL-5
CVS Tags:
DRUPAL-5--1-1
Changes since
1.38: +5 -12 lines
Diff to
previous 1.38
Revert commit 101472 for the DRUPAL-5 branch. This potentially needs
further adaptions in backends and callers (Commit Log, amongst others)
so it's not source compatible, although it shouldn't have caused problems
except when moving the Subversion backend. But let's better be cautious.
Revision
1.38 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sun Feb 17 15:42:28 2008 UTC
(21 months, 1 week ago)
by
jpetso
Branch:
MAIN
Branch point for:
DRUPAL-5
Changes since
1.37: +13 -6 lines
Diff to
previous 1.37
Don't take source item paths into account for the commit action directory
if the corresponding commit action is "modified" or "deleted".
Also document why we do it this way.
Todo:
* Adapt all backends to return the current item for "deleted" actions.
* Adapt Commit Log to show that one instead of the source item.
Revision
1.36 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Tue Feb 12 21:06:04 2008 UTC
(21 months, 1 week ago)
by
jpetso
Branch:
MAIN
Changes since
1.35: +2 -2 lines
Diff to
previous 1.35
Subversion pushes our assumptions about how commit actions can look like
to the next level. Among those assumptions is that modified files
don't change their path and branch: wrong in Subversion, because
moving a parent directory will leave items inside that directory
completely untouched. Only when it's modified afterwards, a commit action
happens for this item, and then it suddenly has a new path.
Branches also don't need to stay the same, as a simple move between
Subversion directories can yield different branches for source and
target item.
This commit removes these assumptions from the API documentation.
Revision
1.35 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sun Feb 10 23:50:23 2008 UTC
(21 months, 2 weeks ago)
by
jpetso
Branch:
MAIN
CVS Tags:
DRUPAL-5--1-0
Changes since
1.34: +5 -1 lines
Diff to
previous 1.34
Don't barf on autoadd updates if nothing is being updated.
(Use case: versioncontrol_hg uses autoadd to create an entry for
remembering the last revision, but only updates it on cronjobs.)
Revision
1.34 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Mon Jan 21 10:52:40 2008 UTC
(22 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.33: +187 -254 lines
Diff to
previous 1.33
Holy moly! Here comes the big fat operation factoring commit.
Commits, branch operations and tag operations now derive from one
base object (an "operation") which has most of its properties stored
in the new {versioncontrol_operation} table.
+ More consolidation, less duplicate code,
and less duplication in the table structure.
+ One operation id to rule them all.
+ Potential for introducing a combined versioncontrol_get_operations()
function that can retrieve all three kinds of operations. Later, though.
+ A few bug fixes.
+ Comes with an upgrade path. Scary, though, I hope I won't ever
have to do an update function like this again.
- Even more abstraction, which makes the database scheme even harder
to grasp.
- One more join in important SQL queries.
Revision
1.33 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sun Jan 13 23:01:18 2008 UTC
(22 months, 1 week ago)
by
jpetso
Branch:
MAIN
Changes since
1.32: +6 -3 lines
Diff to
previous 1.32
Make versioncontrol_ensure_branch() work when the same branch is
requested multiple times in a single run of the script.
Revision
1.32 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Fri Nov 2 13:39:12 2007 UTC
(2 years ago)
by
jpetso
Branch:
MAIN
CVS Tags:
DRUPAL-5--1-0-RC3,
DRUPAL-5--1-0-RC4
Changes since
1.31: +23 -7 lines
Diff to
previous 1.31
Starting the Subversion backend shows quite a bit of buggyness...
but that's fixable:
* Make sure that the delete_{repository,branch,tag,commit}() functions
work from [vcs_backend]_uninstall().
* Make sure that disabled backends never cause *more* results
to be retrieved by the query functions. That bug was the reason
that my test data is now gone. Well it wasn't more than 4 pages anyways.
* Make sure that the FakeVCS backend never handles form value extraction
hooks if it hasn't altered the form beforehand.
* Fix a stupid typo (or rather, copy-n-paste-o) in the FakeVCS backend.
* Polish for the repository edit form: require a repository name,
and remove a duplicate form element description.
Revision
1.31 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Tue Oct 30 01:59:50 2007 UTC
(2 years ago)
by
jpetso
Branch:
MAIN
CVS Tags:
DRUPAL-5--1-0-RC1,
DRUPAL-5--1-0-RC2
Changes since
1.30: +12 -10 lines
Diff to
previous 1.30
Last TODO item for Version Control API 1.0 (code-wise):
Introduce the get_url_log_view() API function and the
'file_log_view' repository URL in the database / repository admin form.
Used by Commit Log for linking file names (whereas the content view URL
is used for linking revision numbers).
Also, a bit of bug fixing:
* Make branch replacement tokens work for repository URLs.
* Delete entries from {versioncontrol_repository_metadata}
if the repository is deleted itself.
* Better URL encoding in Commit Log.
Now let's copy the Version Control API overview from g.d.o and we're set.
Revision
1.30 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Mon Oct 29 21:02:21 2007 UTC
(2 years ago)
by
jpetso
Branch:
MAIN
Changes since
1.29: +37 -37 lines
Diff to
previous 1.29
The right way to write '%d' is without quotes, so remove all of those.
Also, add a few configuration variables to the uninstallation function
that have been forgotten before.
Revision
1.29 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Tue Oct 2 19:48:22 2007 UTC
(2 years, 1 month ago)
by
jpetso
Branch:
MAIN
CVS Tags:
DRUPAL-5--1-0-BETA1
Changes since
1.28: +4 -1 lines
Diff to
previous 1.28
* Fix the calculation of commit directories for top-level commits.
Breaks commitlog's display, but that is another issue.
* Add TODOs for more notification mails that need to be sent out.
Revision
1.28 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sun Sep 23 21:13:15 2007 UTC
(2 years, 2 months ago)
by
jpetso
Branch:
MAIN
CVS Tags:
DRUPAL-5--0-9-RC1
Changes since
1.27: +2 -2 lines
Diff to
previous 1.27
Solve a number of bugs with respect to account authorization and retrieval.
Unfortunately, one problem led to another one, and in the end it all
cumulated in is_account_authorized() requiring a complete repository array
instead of just the repository id.
Which means that caching for get_repositories() is up next.
Revision
1.27 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sun Sep 23 19:46:01 2007 UTC
(2 years, 2 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.26: +17 -6 lines
Diff to
previous 1.26
The Last Great Mess-up: make authorization methods a per-repository setting
instead of a site-wide one. For example, that enables us to have an
application-based contrib repository next to a purely admin-controlled
core one.
Changes that go with this commit:
* One more column in the repository table
* One less column in the account status strings table
* Introduction of hook_versioncontrol_alter_repository_selection()
for selectively disallowing repository registrations
* Reshuffle the admin interface
* While we're at it, move the non-admin pages out of .admin.inc
and into .pages.inc
* Simplify the Account Status module by dropping the
site-wide authorization method, which isn't very practical anyways
* Apidox updates
* ...and a few bug fixes, I think.
Revision
1.26 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Fri Sep 14 09:56:31 2007 UTC
(2 years, 2 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.25: +174 -153 lines
Diff to
previous 1.25
* Add a tag message to the tag operations table.
Optional for the backend (will be supported by all VCSs except CVS).
* Don't query for repositories "WHERE (repo_id = '12' AND repo_id = '12')".
* In _versioncontrol_db_get_additions(), use "primary_key IN ('1','2',...)"
instead of "(primary_key = '1' OR primary_key = '2' OR ...".
* More apidox bulletpointifying. I think versioncontrol should be fine now,
from the apidox point of view.
Revision
1.24 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Mon Sep 3 07:03:54 2007 UTC
(2 years, 2 months ago)
by
jpetso
Branch:
MAIN
CVS Tags:
DRUPAL-5--0-9-BETA1
Changes since
1.23: +13 -13 lines
Diff to
previous 1.23
* A bit of refactoring in the account status module so that we're able
to distinguish between user submitted and programmatically submitted
insertions and updates.
* Together with that, a small API change for more consistency.
* And of course, bug fixes.
Revision
1.21 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Mon Aug 20 09:25:46 2007 UTC
(2 years, 3 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.20: +34 -3 lines
Diff to
previous 1.20
Repository specific overview messages, and a demo mode for showing those
to the admin. Also, better watchdog logging.
Revision
1.19 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sat Aug 18 21:45:52 2007 UTC
(2 years, 3 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.18: +27 -14 lines
Diff to
previous 1.18
* Introduce the mandatory get_{branched,tagged}_items() functions.
* Let "no revision" be the empty string instead of NULL,
in order to reduce confusion for users and backends.
* Some other API documentation updates.
Revision
1.16 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Sat Aug 18 08:58:53 2007 UTC
(2 years, 3 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.15: +2 -2 lines
Diff to
previous 1.15
Fix the .install file (and have the queries sorted in a coherent way).
Also, fix the one issue that coder.module noticed.
Revision
1.15 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Fri Aug 17 18:05:12 2007 UTC
(2 years, 3 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.14: +481 -90 lines
Diff to
previous 1.14
Centralize branches and tags into the API module.
This is a major change, and I've got no idea if everything still works.
At the moment, it probably doesn't... but it will.
Revision
1.13 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Wed Aug 15 14:06:32 2007 UTC
(2 years, 3 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.12: +140 -102 lines
Diff to
previous 1.12
Improve the branch/tag API for more ease of use and flexibility.
Also, introduce versioncontrol_get_affected_item($commit_action)
in order to share a bit of code and prevent incorrect checks.
Revision
1.10 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Mon Aug 13 09:44:38 2007 UTC
(2 years, 3 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.9: +27 -35 lines
Diff to
previous 1.9
Generalize the repository/account hooks so that all modules can provide
additional edit/add form elements (and more importantly, process them)
instead of just the backend modules.
Revision
1.9 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Fri Aug 10 16:16:14 2007 UTC
(2 years, 3 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.8: +108 -31 lines
Diff to
previous 1.8
A first stab at a commit restriction determination function for backends,
including the hook_versioncontrol_commit_access() for other modules.
Revision
1.8 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Thu Aug 9 16:38:29 2007 UTC
(2 years, 3 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.7: +5 -3 lines
Diff to
previous 1.7
Move the menu hook to the main file, add a JavaScript username callback,
and only return approved accounts by default. (Account approval can be
denied by implementing hook_versioncontrol_is_account_approved($uid, $repo_id)
and returning FALSE for bad users.)
Revision
1.7 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Fri Aug 3 14:06:02 2007 UTC
(2 years, 3 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.6: +138 -72 lines
Diff to
previous 1.6
Provide account creation and modification facilities
(still without motivation texts and admin approval for now).
Simplify and complete the backend API.
Revision
1.6 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Thu Aug 2 12:11:17 2007 UTC
(2 years, 3 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.5: +318 -14 lines
Diff to
previous 1.5
Fixes, improvements, introduction of a get_repository() convenience
function, and completing the implementation of the insert/update/delete API
for commits, repositories and accounts.
Revision
1.5 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Mon Jul 30 12:18:46 2007 UTC
(2 years, 3 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.4: +49 -1 lines
Diff to
previous 1.4
Centralize account management (insertion and retrieval, for now)
and split out the repository URLs into a separate table.
Revision
1.4 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Mon Jul 23 08:49:07 2007 UTC
(2 years, 4 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.3: +2 -2 lines
Diff to
previous 1.3
Replace 'internal' arrays with '[vcs]_specific' ones.
Also, improve some bits of API documentation and fix copyright headers.
Revision
1.3 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Thu Jul 19 17:32:26 2007 UTC
(2 years, 4 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.2: +3 -3 lines
Diff to
previous 1.2
Update all occurrences of the AUTOADD_COMMIT and AUTOADD_REPOSITORY flags
so that they appear correctly in all places. If I'm right, xcvs-loginfo
works perfectly now. Whoo!
Revision
1.2 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Thu Jul 19 17:06:00 2007 UTC
(2 years, 4 months ago)
by
jpetso
Branch:
MAIN
Changes since
1.1: +6 -4 lines
Diff to
previous 1.1
Bugfixes all over the place. Also, remove versioncontrol-bootstrap.php,
it's not needed anymore as the required code has grown so small that it
fits into xcvs-config.php (and other hook scripts) without a doubt.
Revision
1.1 -
(
view)
(
download)
(
as text)
(
annotate)
-
[select for diffs]
Thu Jul 19 12:27:54 2007 UTC
(2 years, 4 months ago)
by
jpetso
Branch:
MAIN
Oh right, there's two new files.
Say hello to versioncontrol-backend.inc which contains the backend-only
part of the API, and versioncontrol-bootstrap.php which provides an
easy-to-use way to get Drupal bootstrapped from hook scripts.
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.
