Date: Thu, 24 Sep 2009 21:49:29 +0400 From: Andrey Dibrov X-Mailer: The Bat! (v4.0.18) Professional Organization: Softdev X-Priority: 3 (Normal) Message-ID: <1155805319.20090924214929@softdev.spb.ru> To: Andy Levy Subject: Re[2]: public/private commits In-Reply-To: References: <1957060437.20090924143232@softdev.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: quoted-printable =FA=C4=D2=C1=D7=D3=D4=D7=D5=CA=D4=C5, Andy. =F7=D9 =D0=C9=D3=C1=CC=C9 24 =D3=C5=CE=D4=D1=C2=D2=D1 2009 =C7., 14:51:20: > On Thu, Sep 24, 2009 at 06:32, Andrey Dibrov wro= te: >> =FA=C4=D2=C1=D7=D3=D4=D7=D5=CA=D4=C5, Users. >> >> I uses SVN a long time, so i find out what SVN still doesn't have >> someone feature. It will be very useful to organize into future >> version of SVN new feature for commit action. Developers sometimes >> wants to make commits for yourself to hide changes from other >> developers in trunk or in branch. This is very useful if you want to com= mit >> not complete or not enough tested changes to server, go home or other pl= ace >> and take public update plus self private (not public) update to complete= changes >> and make later public commit. >> Does this feature with public/private commit already exist? > Commit your "in progress" work to a branch you create, when complete > merge your changes back to a common location (trunk or another > branch). This is really ambiguous to create branch per developer. > Developers working together on a project should almost never have a > need to hide things from each other. It's not good for the team. Better doesn't see broken sources, than gonna get broken build. Team shouldn't see private commit, it is useful only for developer who made it. --=20 =F3 =D5=D7=C1=D6=C5=CE=C9=C5=CD, Andrey mailto:adibrov@softdev.spb.ru