All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Govind Salinas" <blix@sophiasuchtig.com>
Cc: "Jeff King" <peff@peff.net>,
	"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
	"Jay Soffian" <jaysoffian@gmail.com>,
	"Jason Garber" <jgarber@ionzoft.com>,
	git@vger.kernel.org
Subject: Re: [PATCH(TIC)] push: annoy all users by deprecating the default semantics
Date: Tue, 19 Feb 2008 17:10:02 -0800	[thread overview]
Message-ID: <7vr6f8e8lx.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <5d46db230802191703v1e273284k71817fcd8a2639a1@mail.gmail.com> (Govind Salinas's message of "Tue, 19 Feb 2008 19:03:23 -0600")

"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.

  reply	other threads:[~2008-02-20  1:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-18 22:15 git push [rejected] question Jason Garber
2008-02-19  4:33 ` Jeff King
2008-02-19 13:09   ` Jay Soffian
2008-02-19 15:08     ` Jeff King
2008-02-19 15:18       ` Jay Soffian
2008-02-19 15:25         ` Jeff King
2008-02-19 15:59           ` Johannes Schindelin
2008-02-19 16:14           ` [PATCH(TIC)] push: annoy all users by deprecating the default semantics Johannes Schindelin
2008-02-19 16:21             ` Jason Garber
2008-02-19 16:41               ` Johannes Schindelin
2008-02-19 16:37             ` Jeff King
2008-02-19 16:54               ` Johannes Schindelin
2008-02-19 17:05                 ` Jeff King
2008-02-20  1:03                   ` Govind Salinas
2008-02-20  1:10                     ` Junio C Hamano [this message]
2008-02-20  1:21                       ` Govind Salinas
2008-02-20  3:15                         ` Junio C Hamano
2008-02-19 18:40               ` Jay Soffian
     [not found]     ` <E7DE807861E8474E8AC3DC7AC2C75EE50542F62D@34093-EVS2C1.exchange.rackspace.com>
2008-02-19 15:21       ` git push [rejected] question Jeff King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vr6f8e8lx.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=blix@sophiasuchtig.com \
    --cc=git@vger.kernel.org \
    --cc=jaysoffian@gmail.com \
    --cc=jgarber@ionzoft.com \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.