From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Steffen Prohaska <prohaska@zib.de>
Cc: Junio C Hamano <gitster@pobox.com>,
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 11:23:23 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0711221120300.27959@racer.site> (raw)
In-Reply-To: <7E8CB606-6CBD-4736-A2CB-0A1E1BD219D3@zib.de>
Hi,
On Thu, 22 Nov 2007, Steffen Prohaska wrote:
> git checkout -b foo origin/master
> work work work
> git checkout -b bar origin/master
> work work work
> git checkout foo
> git pull # or git fetch; git rebase
> git push
> git checkout bar
> git branch -d foo
> work work, ... and later push bar, too
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. (Okay, there is this
other thing where people say "git push origin master:master" and I still
do not know where they got _that_ from.)
I would _never_ teach people to be sloppy here. Even if you introduce
whatever appears convenient to you. IMHO this is not only giving rope,
but close to putting the noose around the neck.
Ciao,
Dscho
next prev parent reply other threads:[~2007-11-22 11:23 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 [this message]
2007-11-22 11:49 ` Junio C Hamano
2007-11-22 11:59 ` Andreas Ericsson
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=Pine.LNX.4.64.0711221120300.27959@racer.site \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).