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

From: Govind Salinas <blix@sophiasuchtig.com>
Date: Feb 20, 2008, 01:21 UTC
Message-ID: <5d46db230802191721p527c0a85k362c7b364c7e99c4@mail.gmail.com>
In-Reply-To: <7vr6f8e8lx.fsf@gitster.siamese.dyndns.org>

On 2/19/08, Junio C Hamano <gitster@pobox.com> wrote:

Show 22 quoted lines

> "Govind Salinas" <blix@sophiasuchtig.com> writes:
>
> > 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.
>
> For both counts, it feels so much like Cogito.
>
> I would not comment on "the most common" adjective, but I am
> still a big believer of "core git gives common foundation for
> Porcelains that support different workflows to talk with each
> other" ideal, and I really like that you are building a
> Porcelain that would suit your favorite workflow.
>
>

Once I have it in better shape, I hope to get commentary from the rest of the git users on how their workflows go and see where I can simplify things or where they need to be more complex. I don't want it to _just_ be for my workflow. I want something that appeals to the common user (if there is such a thing, and with git, I don't know that you can say that).

-Govind