Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion git-flow AVH Edition 1.1.0 Released
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Mark Derricutt  
View profile  
 More options Aug 5 2012, 7:27 pm
From: Mark Derricutt <m...@talios.com>
Date: Mon, 6 Aug 2012 11:27:48 +1200
Local: Sun, Aug 5 2012 7:27 pm
Subject: Re: git-flow AVH Edition 1.1.0 Released

Strange, when I release my branch now using this AVH branch I see:

Summary of actions:
- Release branch 'release/6.0.20' has been merged into 'master'
- The release was tagged '6.0.20'
/Users/amrk/Dropbox/gitflow-avh/gitflow-common: line 65: [: -eq: unary
operator expected
/Users/amrk/Dropbox/gitflow-avh/gitflow-common: line 65: [: -eq: unary
operator expected
- Release branch 'release/6.0.20' 'has been deleted
- You are now on branch 'master'

This is on OSX.  Also, the commit I see back into develop now reads:

    Merge tag '6.0.20' into develop

normally its merge branch release/xxx into develop - and I just had what
looked like a REALLLLY old branch get merged into my development branch for
one project - corresponding to this tag merge, which is odd....

--
"Great artists are extremely selfish and arrogant things" — Steven Wilson,
Porcupine Tree

On Wed, Aug 1, 2012 at 8:26 AM, Mark Derricutt <m...@talios.com> wrote:
> Awesome, will have to check this out - hadn't actually seen your forked
> branch before.

> Is the AVH edition a total fork of nvies' never to merge? I see a few
> commits on nvie's repository that don't merge into AVH ( altho I suspect
> some of them have already been superseeded with changes on the AVH release
> )?

> Do you have a list of all changes/differences?

> On 28/07/2012, at 7:00 AM, Peter van der Does <pvanderd...@gmail.com>
> wrote:

> Today we released a new version of git-flow AVH Edition. You can download<http://goo.gl/2Dbs7>the version or check the full code on the github
> page <http://goo.gl/9hGZ3>

> Some release notes:

>    -

>    Add the ability to keep/delete local/remote branches on finish.
>    When finishing a release/hotfix/feature you now can keep/delete the
>    local/remote release/hotfix/feature branch.
>    -

>    New command: git flow release branch
>    With this command you can directly release a given branch. There is no
>    need to start a new release and finish it. You can not use this command on
>    the git-flow branches feature/hotfix/release/support.
>    -

>    Support reading the tag message from a file in release/hotfix finish.
>    Add the option -f,--messagefile to release and hotfix finish.
>    -

>    The sub-commands feature, release and hotfix now have a new
>    sub-action, delete.
>    With that action you can delete the branches, locally and remote. The
>    action has two options, -f and -r. With -f you can force the deletion, even
>    when the to be deleted branch was not merged yet. With -r the remote branch
>    will also be deleted.

>    - Feature and Release squashing options.
>    This allows a -S option to both feature and releasing finishing
>    actions so that developers can squash commits into one large one.

> For a complete look on the changes check out the Changelog<http://goo.gl/DRNTG>on github.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.