Let backends define default plugins

So, i.e. git backend could select a reposync plugin for it.

Comments

Comment #1

marvil07 commented 25 April 2012 at 22:15

Project:	Version Control API -- Git backend	» Version Control API
Version:	7.x-1.x-dev	» 6.x-2.x-dev
Component:	Code	» API module

it should be d7, but there seems to be a cache on the comment version field.

Log in or register to post comments

Comment #2

marvil07 commented 26 April 2012 at 06:57

Status:

Active

» Fixed

Commit added to upstream.

Log in or register to post comments

Comment #3

10 May 2012 at 07:00

Automatically closed -- issue fixed for 2 weeks with no activity.

Log in or register to post comments

Comment #4

11 April 2014 at 17:46

Commit 61eda72 on 7.x-1.x, repository-families, drush-vc-sync-unlock by marvil07:
```
Issue #1548006: Let backends define default plugins.

Actually the...
```
Commit 8dc5e21 on sync-tinkering-d7, repository-families, drush-vc-sync-unlock by marvil07:
```
Issue #1548006: Let backends define default plugins.

Actually the...
```

Log in or register to post comments

Comment #5

15 April 2014 at 22:25

Commit 61eda72 on 7.x-1.x, repository-families by marvil07:

Issue #1548006: Let backends define default plugins.

Actually the...

Commit 8dc5e21 on sync-tinkering-d7, repository-families by marvil07:

Issue #1548006: Let backends define default plugins.

Actually the...

Log in or register to post comments