Re: antisocial things you can do in git (but not CVS)

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Abhijit Menon-Sen <ams(at)toroid(dot)org>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: antisocial things you can do in git (but not CVS)
Date: 2010-07-21 11:09:22
Message-ID: AANLkTily8y27u7zc60TdHpxKtLmt3VDyOCJGqRsHU0AU@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 21, 2010 at 13:05, Abhijit Menon-Sen <ams(at)toroid(dot)org> wrote:
> At 2010-07-21 12:55:55 +0200, magnus(at)hagander(dot)net wrote:
>>
>> We are not changing the workflow, just the tool.
>
> OK, but I don't see why accidental merge commits need to be considered
> antisocial, and banned or rebased away. Who cares if they exist? They
> don't change anything you need to do to pull, create, view, or push
> changes.

They makes it harder to track how the project has moved along for
people who don't really know about the concept.

I'm not sure, but I bet they may cause issues for those tracking the
project through git-cvs, or any other tool that doesn't deal with
nonlinear history.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-07-21 11:28:02 Re: patch: to_string, to_array functions
Previous Message Abhijit Menon-Sen 2010-07-21 11:05:17 Re: antisocial things you can do in git (but not CVS)