diff options
author | Dickson S. Guedes | 2011-10-12 18:16:06 +0000 |
---|---|---|
committer | Dickson S. Guedes | 2011-10-12 18:16:06 +0000 |
commit | ef10e820f22f190a2a16dfc06b15a7b6f645b7d4 (patch) | |
tree | 66440e87fe9cb7a60d6c6a9d6113292218516a97 | |
parent | eb2af742a0b483b4587ed1c591a06740652885ae (diff) |
fixing git url on README, ref #17git-support
-rw-r--r-- | README.md | 4 | ||||
-rw-r--r-- | Rakefile | 4 |
2 files changed, 4 insertions, 4 deletions
@@ -157,8 +157,8 @@ You can start a new extension with git support calling `skeleton` task with `--git` flag, then in addition to create skeleton, `pgxn-utils` will initialize a git repository and do a initial commit. -Once you have you extension in a git repository your `bundle` will use only the -commited files to create the archive, but if your repository is dirty `pgxn-utils` +Once you have your extension in a git repository your `bundle` will use only the +commited files to create the archive, but if your repository is dirty then `pgxn-utils` will hint you to commit or stash your changes, before bundle. You must be careful with new files not added to repository, because they will NOT @@ -106,8 +106,8 @@ You can start a new extension with git support calling `skeleton` task with `--git` flag, then in addition to create skeleton, `pgxn-utils` will initialize a git repository and do a initial commit. -Once you have you extension in a git repository your `bundle` will use only the -commited files to create the archive, but if your repository is dirty `pgxn-utils` +Once you have your extension in a git repository your `bundle` will use only the +commited files to create the archive, but if your repository is dirty then `pgxn-utils` will hint you to commit or stash your changes, before bundle. You must be careful with new files not added to repository, because they will NOT |