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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
