www-infrastructure-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henning Schmiedehausen <...@intermeta.de>
Subject Re: [dSCM] Use case: new committer
Date Thu, 01 May 2008 17:35:32 GMT
You are probably talking about r652498.

That is not a dSCM, cSCM or anything else problem. This is purely a
"developers too lazy too split" problem. If the shindig project is fine
with this commit, then who cares. I would probably let the developer
revert and re-apply in smaller chunks. But this is open source. :-)

	Best regards

On Thu, 2008-05-01 at 18:09 +0200, Santiago Gala wrote:
> I just wanted to launch a use case for a distributed SCM integration,
> including a concrete example. Just today, a new committer in shindig,
> committed a big chunk of code. This was because there were problems with
> his password and all together, he had almost one month delay from being
> accepted as a committer and being able to effectively commit.
> Instead of: one big commit of
> 120 files changed, 7404 insertions(+), 3790 deletions
> he could have committed the 20 tematic commiits that probably this work
> consisted of. Ha would have kept them (merging or even attaching to
> issue tracker items) all the work in nice logically related units until
> he had the ability to push this work forward to the common repository.
> Regards
> Santiago
Henning P. Schmiedehausen  -- hps@intermeta.de | JEE, Linux, Unix
91054 Buckenhof, Germany   -- +49 9131 506540  | Apache Java Software
Open Source Consulting, Development, Design    | 

INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350
Gesellschaftssitz: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen

  char name_buf[257];           /* max unix filename is 256, right? */

View raw message