From: Martin Langhoff <martin.langhoff@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Please discuss: what "git push" should do when you do not say what to push?
Date: Tue, 20 Mar 2012 14:31:19 -0400 [thread overview]
Message-ID: <CACPiFCLbTA=AwymUOde43Z61t9cd5O=uk_hs5Dt6WZhYYg06zA@mail.gmail.com> (raw)
In-Reply-To: <7vy5qv70mh.fsf@alter.siamese.dyndns.org>
On Tue, Mar 20, 2012 at 11:28 AM, Junio C Hamano <gitster@pobox.com> wrote:
> As many people already said in the discussion before the RFD message that
> is at the root of this thread, the name of the option --force alone
> already signals it is something you use after thinking twice.
Definitely. You may think twice about the branch you' re planning to
force-update. "Do I really want to force-update <this>?". But it
doesn't mean you know and fully understand the "push default" rules of
git.
With "immediately" I mean "sooner than several releases away".
In any case, seems I missed the train and the discussion is closed;
I'll head back to my cave.
cheers,
m
--
martin.langhoff@gmail.com
martin@laptop.org -- Software Architect - OLPC
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
next prev parent reply other threads:[~2012-03-20 18:31 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 5:10 Please discuss: what "git push" should do when you do not say what to push? Junio C Hamano
2012-03-17 5:22 ` Junio C Hamano
2012-03-17 10:05 ` Andrew Sayers
2012-03-18 18:50 ` Junio C Hamano
2012-03-18 21:26 ` Ævar Arnfjörð Bjarmason
2012-03-19 0:29 ` Junio C Hamano
2012-03-19 7:29 ` Sebastien Douche
2012-03-19 20:11 ` Andrew Sayers
2012-03-19 21:43 ` Junio C Hamano
2012-03-19 22:20 ` demerphq
2012-03-19 22:38 ` Junio C Hamano
2012-03-20 10:00 ` Andreas Ericsson
2012-03-19 22:47 ` Andrew Sayers
2012-03-19 22:59 ` Junio C Hamano
2012-03-20 21:20 ` Andrew Sayers
2012-03-20 23:09 ` Junio C Hamano
2012-03-20 23:41 ` Andrew Sayers
2012-03-21 0:25 ` Junio C Hamano
2012-03-20 14:12 ` Martin Langhoff
2012-03-20 15:28 ` Junio C Hamano
2012-03-20 18:31 ` Martin Langhoff [this message]
2012-03-20 16:43 ` Jakub Narebski
2012-03-21 17:54 ` Summary of discussion on "git push" default change Junio C Hamano
2012-03-21 18:05 ` Matthieu Moy
2012-03-17 14:00 ` Please discuss: what "git push" should do when you do not say what to push? Joey Hess
2012-03-19 0:36 ` Junio C Hamano
2012-03-17 18:43 ` fREW Schmidt
2012-03-18 4:02 ` H. Peter Anvin
2012-03-18 5:43 ` Marcus D. Hanwell
2012-03-18 16:52 ` Sebastian Schuberth
2012-03-19 9:07 ` Peter Krefting
2012-03-19 9:35 ` Letting remote repositories override local configuration Jonathan Nieder
2012-03-19 12:21 ` Peter Krefting
2012-03-19 18:57 ` Please discuss: what "git push" should do when you do not say what to push? Kevin Ballard
2012-03-20 2:27 ` Antony Male
2012-03-20 12:04 ` Jakub Narebski
2012-03-20 13:04 ` Antony Male
2012-03-20 7:13 ` Nathan Gray
2012-03-20 12:00 ` Ben Tebulin
2012-03-20 12:00 ` Ben Tebulin
2012-03-20 12:00 ` Ben Tebulin
2012-03-20 12:01 ` Ben Tebulin
2012-03-20 12:36 ` Filipe Fernandes
-- strict thread matches above, loose matches on Subject: below --
2012-03-19 18:26 Michael K. Johnson
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='CACPiFCLbTA=AwymUOde43Z61t9cd5O=uk_hs5Dt6WZhYYg06zA@mail.gmail.com' \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).