Re: [Rails-devel] Git branches

[Stefan F. <ste...@we...>]

I meant "private" as opposite to "official", not opposite to "public".
So a branch, that is not one of the officials, but one that needs either 
backup and/or is of interest for others.

Maybe you have a better idea how to backup long-running branches, that 
are only used by one developer?

On 02/10/2014 03:52 PM, brett lentz wrote:
>
>
> On Mon, Feb 10, 2014 at 4:13 AM, Stefan Frey <ste...@we...
> <mailto:ste...@we...>> wrote:
>
>     There are no more and more branches on the git repo, I repeat my
>     proposal from some time ago:
>
>     A) Let us have "official" branches which start with rails_1 or rails_2,
>     and have all others indicate the developer you owns or started the
>     branch. Thus e.g. I rename mine to "sfy_route" or
>     "sfy_rails_2_unfinished".
>
>
> +1 to standardized naming of official branches.
>
>     B) And it should be possible to delete old private branches, especially
>     those that have been merged already. This can be checked using with the
>     command "git branch --merged". Branches are only tags to specific
>     commits, so they have nothing special.
>
>
> Anybody with commit rights can remove branches by doing this:  git push
> :some_branch
>
> The command syntax for push is "git push [src]:[dst]", so the command
> for deleting branches is basically, "push null source to the remote branch."
>
> A point of clarification. Private branches are branches that you don't
> push anywhere. If you push a branch to the SF.net repository, it's no
> longer private.
>
> Names for private branches are the concern of each developer because
> nobody else is going to see those branches.
>
> For public branches that aren't a part of the primary release process
> (i.e. branches with in-development code you're pushing to share your
> ideas with other developers.), those should have a clear naming
> convention to reduce confusion for the release manager.
>
>
>     This would make life easier for all of us.
>
>     What are the opinions of the others?
>
>
> This is all fine by me.
>
> ---Brett.
>
>
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>