Re: [PATCH(TIC)] push: annoy all users by deprecating the default semantics

["Govind Salinas" <blix@sophiasuchtig.com>]

On 2/19/08, Jeff King <peff@peff.net> wrote:
> On Tue, Feb 19, 2008 at 04:54:14PM +0000, Johannes Schindelin wrote:
>
> > > Just say "git push origin HEAD"?
> >
> > The point is: if that becomes the default (with a certain config option),
> > people will get used to typing "git push".  They will not even _know_
> > about the explicit form.
>
> I guess I hoped that people giving answers on the IRC channel would be a
> little less clueless. Perhaps that is just optimism.
>
> > See followup.
>
> I'm actually starting to like your patch now...;)
>
> > BTW if that is really the way to go, we will have to have a _long_ period
> > (I am talking about 6-12 _months_ if not more) where there _must not_ be a
> > default action for git-push.  Otherwise people _will_ get more confused
> > than necessary.
>
> I agree that it would need a long deprecation period to change behavior.
> It would almost be easier to have a "git <foo>" command where <foo> is
> some sort of restricted, safe-for-certain-workflows version of push.
>

For those interested, this is how I plan to have the default for
pyrite.  The default currently just calls "git push origin HEAD"
Calling with another target repository and refspec would still be
supported of course.

In general, the plan it to take the most common work flows and simply
the UI around those.  This includes silently doing "git add -u" before
pushing a commit and "pyt diff" will diff between the working
directory and HEAD because I have never been interested in the state
of the index, only in the state of the working dir.

-Govind