2. I've chosen a prefix for published branches that may be rebased,
"devo/". I then make sure to communicate to the rest of the team that
it's not safe to base any work on branches named liked that.


Just out of curiosity: why "devo"? :-)
Is it by chance related to some term related to "development" in your
native language?

Because once the code is in the devo branch he can whip it into shape, shape it up, get it straight, go forward, move ahead, try to detect it, if it's not too late.

*couldn't resist*


On 29 Dec 2015, at 5:00, Konstantin Khomoutov wrote:

On Mon, 28 Dec 2015 22:07:38 +0100
Magnus Therning <mag...@therning.org> wrote:

[...]
2. I've chosen a prefix for published branches that may be rebased,
"devo/". I then make sure to communicate to the rest of the team that
it's not safe to base any work on branches named liked that.

Just out of curiosity: why "devo"? :-)
Is it by chance related to some term related to "development" in your
native language?

--
You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Git for 
human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to