Re: documentation for committing with git

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: David Christensen <david(at)endpoint(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: documentation for committing with git
Date: 2010-07-21 19:31:11
Message-ID: 1279740624-sup-4827@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Excerpts from Robert Haas's message of mié jul 21 15:26:47 -0400 2010:

> > So you're working on some back branch, and make a WIP commit so you can switch to master to make a quick commit.  Create a push on master.  Bare git push.  WIP commit gets pushed upstream.  Oops.
>
> Sure, oops, but I would never do that. I'd stash it or put it on a
> topic branch.

Somebody else will. Please remember you're writing docs that are not
for yourself.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2010-07-21 19:34:06 Re: antisocial things you can do in git (but not CVS)
Previous Message Alvaro Herrera 2010-07-21 19:29:04 Re: managing git disk space usage