pg.ddx.io pgsql-hackers@postgresql.org mailing list archive
help / color / mirror / Atom feedFrom: Andres Freund <andres@anarazel.de>
To: Greg Stark <stark@enterprisedb.com>
Cc: Markus Wanner <markus@bluegap.ch>
Cc: Marko Kreen <markokr@gmail.com>
Cc: Aidan Van Dyk <aidan@highrise.ca>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PostgreSQL Developer meeting minutes up
Date: Wed, 03 Jun 2009 14:19:34 +0200
Message-ID: <4A266A56.2020703@anarazel.de> (raw)
In-Reply-To: <4136ffa0906030508i2971790dk54a8203ee03ed196@mail.gmail.com>
References: <20090526144812.GC15213@yugib.highrise.ca>
<e51f66da0906012343r46aaeef1ve38a442140821412@mail.gmail.com>
<e51f66da0906020013w1f4152f5xd7c1287eb77d4f00@mail.gmail.com>
<20090602134831.186767ksvmsgj8gf@mail.bluegap.ch>
<e51f66da0906020546l578e56c8m52f5a6e10760eaf9@mail.gmail.com>
<20090602162333.369974jcc3jpn3dx@mail.bluegap.ch>
<e51f66da0906020834q7e6e3401jf77f40f9924bbace@mail.gmail.com>
<20090602180702.15986cp384yo3l7q@mail.bluegap.ch>
<e51f66da0906020917m274debd5u3288d6d56b62daf7@mail.gmail.com>
<20090603131004.12934iyrr4f7rlsc@mail.bluegap.ch>
<4136ffa0906030508i2971790dk54a8203ee03ed196@mail.gmail.com>
Hi,
On 06/03/2009 02:08 PM, Greg Stark wrote:
> On Wed, Jun 3, 2009 at 12:10 PM, Markus Wanner<markus@bluegap.ch> wrote:
> That would make the git history match Tom's "same commit message"
> implicit CVS history that cvs2pcl was giving him. I find git-log's
> output including merge commits kind of strange and annoying myself but
> having them at least gives us a chance to have a tool that understands
> them output something like cvs2pcl.
"git log --no-merges" hides the actual merge commits if that is what you
want.
Andres
view thread (83+ messages) latest in thread
Message-ID: <4A266A56.2020703@anarazel.de>
Permalink: ../4A266A56.2020703@anarazel.de/
Also on: postgresql.org/message-id/4A266A56.2020703@anarazel.de
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: andres@anarazel.de, stark@enterprisedb.com, markus@bluegap.ch, markokr@gmail.com, aidan@highrise.ca, heikki.linnakangas@enterprisedb.com, magnus@hagander.net, andrew@dunslane.net
Subject: Re: PostgreSQL Developer meeting minutes up
In-Reply-To: <4A266A56.2020703@anarazel.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox