Re: [RFC] git-publish

From: Junio C Hamano <junkio@cox.net>
Date: Aug 13, 2006, 17:07 UTC
Message-ID: <7vzme8lg28.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.64.0608131158500.9789@iabervon.org>

Daniel Barkalow <barkalow@iabervon.org> writes:

> My suspicion is that most people who run commit directly and have a 
> default push location tend to want to push after every commit (or, at 
> least, be fine with that, and really want to have pushed after the last of 
> a batch).

I for one would be horrified ;-) but that's probably just me.

Some people seem to like 'commit -o' (which now is the default), and worse yet (from 'discipline' point of view) there are even people who want to be able to edit the patch preview in place in 'commit -v' buffer. Commits by these people are by definition not even compile tested in isolation. I suspect those are the very people who would want to push immediately after they make commits.

Chilly.

Don't get me wrong -- I am not opposed to "git-commit && git-push". It may be handy if you are pushing into some alternate (backup) location. But "publish" (implying "public consumption") is too much for my taste, and I am hesitant to endorse such a workflow.