From: Andreas Ericsson <ae@op5.se>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Steffen Prohaska <prohaska@zib.de>,
Nico -telmich- Schottelius <nico-linux-git@schottelius.org>,
git@vger.kernel.org
Subject: Re: Adding push configuration to .git/config
Date: Thu, 22 Nov 2007 12:59:04 +0100 [thread overview]
Message-ID: <47456F08.5020606@op5.se> (raw)
In-Reply-To: <7v7ika5wld.fsf@gitster.siamese.dyndns.org>
Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
>> I have to say that I slowly grow an antipathy for "git push" without
>> parameters. _All_ of the confusions with push that I saw stem from being
>> too lazy to say where and what you want to push.
>
> The same thing can be said for "fetch" by the way.
I disagree, since "fetch" at worst will auto-update the remote-tracking
branches only, while "push" may publish changes that are downright
wrong and never meant for publishing. What's worse is that fixing up
published history is a whole lot messier than it is to fix ones own
remote-tracking branches.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2007-11-22 11:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 10:55 Adding push configuration to .git/config Nico -telmich- Schottelius
2007-11-21 22:02 ` Steffen Prohaska
2007-11-22 1:48 ` Junio C Hamano
2007-11-22 7:08 ` Steffen Prohaska
2007-11-22 7:52 ` Andreas Ericsson
2007-11-22 8:28 ` Junio C Hamano
2007-11-22 8:23 ` Junio C Hamano
2007-11-22 8:54 ` Steffen Prohaska
2007-11-22 11:23 ` Johannes Schindelin
2007-11-22 11:49 ` Junio C Hamano
2007-11-22 11:59 ` Andreas Ericsson [this message]
2007-11-22 18:22 ` Steffen Prohaska
2007-11-28 22:15 ` Nico -telmich- Schottelius
2007-11-28 23:50 ` Johannes Schindelin
2007-11-29 22:46 ` Junio C Hamano
2007-11-30 0:37 ` Jakub Narebski
-- strict thread matches above, loose matches on Subject: below --
2007-11-23 13:07 MichaelTiloDressel
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=47456F08.5020606@op5.se \
--to=ae@op5.se \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nico-linux-git@schottelius.org \
--cc=prohaska@zib.de \
/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.