The advantage, for me, is not to have to look for the git commands and their switches to update my local files into the remote (or init if it is the first time). I just do make git-push and all my local changes are pushed onto the remote, ready for end users to use it. First time or Nth time, this can be run repeatedly, every time I need to update the remote with my local changes.
It's bad enough to have to remember every time how to make available to git my public key, I just refuse to learn git nomenclature. It is very likely that the git commands I am using are not entirely fit - I was under the impression that git push will forward all local changes to remote. If you need something else, then just create another target. The main idea is still the same.
The obvious disadvantage of my method is that Makefile.PL now contains a target (git-push) which the end user should never need.
In reply to Re^2: git-push target for Makefile (via ExtUtils::MakeMaker)
by bliako
in thread git-push target for Makefile (via ExtUtils::MakeMaker)
by bliako
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |