This project is archived and is in readonly mode.
[PATCH] Install Plugin: pass -b/--branch BRANCH for git plugins and -r/--revision REVISION for git/subversion plugins
-
Prem Sichanugrist (sikachu)
- State changed from new to open
- Assigned user set to José Valim
- Milestone cleared.
I only see the patch for Git, is that correct?
I somewhat think this is a good idea, but then will it be much slower using
git pullwithout--depth?Anyway, if the speed is not the problem, then I think this would help so that people wouldn't have to specify specific ref on that brach, for instance if they want to install the
obsoletebranch. -
Juice
yeah, I only add the patch for git.
as I test,I don't think it will be much slower. ;)
there is another version, in this version, it's will keep the
--depth 1unless you specify the--revision.thanks.
-
Jeremy Kemper
This can use
--revision branchname, doesn't need a new option. -
Juice
yeah, I know that, there is no document.and not easy to understand.
this patch provide more options, you can install a plugin by branchname and commit ref
-
Jeremy Kemper
- State changed from open to wontfix
-1 on adding more options that do the same thing. Better to improve the docs.
-
Juice
do you think they are doing the same thing? can you install plugin by
commit's refrightnow?
I think you totally misunderstood me. -
Jeremy Kemper
Maybe I totally misunderstand: you added support for installing a specific revision, then you added support for --branch.
In git, these are both refs. You're installing a plugin at a specific ref, whether it's a revhash or a branch or a tag.
So we only need one option. Ideally, this would be an argument instead of a special option, and it would default to "master"
(Keeping the same options as svn is not necessary, either.)
