From: Dickson S. Guedes Date: Wed, 12 Oct 2011 18:16:06 +0000 (-0300) Subject: fixing git url on README, ref #17 X-Git-Url: http://git.postgresql.org/gitweb/stat%3Cscript%20data-cfasync=?a=commitdiff_plain;h=refs%2Fheads%2Fgit-support;p=pgxn-utils.git fixing git url on README, ref #17 --- diff --git a/README.md b/README.md index df911d0..782a02d 100644 --- a/README.md +++ b/README.md @@ -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 diff --git a/Rakefile b/Rakefile index f373afd..67f775a 100644 --- a/Rakefile +++ b/Rakefile @@ -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