Hello, all. We've switched to git some time ago, now we should have some
kind of workflow documents. In particular I think of following points:
- Developpers with commit access can create branches as they see fit as
long as it's prefixed by their name and they don't do sth nasty like
storing binary
Vladimir 'φ-coder/phcoder' Serbinenko, 2013-11-10 19:01 (Europe/Helsinki):
Hello, all. We've switched to git some time ago, now we should have some
kind of workflow documents. In particular I think of following points:
- Developpers with commit access can create branches as they see fit as
long a
В Thu, 14 Nov 2013 15:20:10 +0200
Mikko Rantalainen пишет:
> Vladimir 'φ-coder/phcoder' Serbinenko, 2013-11-10 19:01 (Europe/Helsinki):
> > Hello, all. We've switched to git some time ago, now we should have some
> > kind of workflow documents. In particular I think of following points:
> > - Dev
I don't like the idea of double work to essentially have 2 commit messages.
But it's possible to remove Changelog file. I'd like to know if any other
major gnu projects made the move.
On Nov 25, 2013 7:27 PM, "Andrey Borzenkov" wrote:
> В Thu, 14 Nov 2013 15:20:10 +0200
> Mikko Rantalainen пишет
В Thu, 28 Nov 2013 07:45:00 +0100
"Vladimir 'phcoder' Serbinenko" пишет:
> I don't like the idea of double work to essentially have 2 commit messages.
> But it's possible to remove Changelog file. I'd like to know if any other
> major gnu projects made the move.
Oh, I did not dare to ask but if
On Thu, Nov 28, 2013 at 09:26:36PM +0400, Andrey Borzenkov wrote:
> В Thu, 28 Nov 2013 07:45:00 +0100
> "Vladimir 'phcoder' Serbinenko" пишет:
> > I don't like the idea of double work to essentially have 2 commit messages.
> > But it's possible to remove Changelog file. I'd like to know if any oth
