From: Ivan Shmakov <ivan@siamics.net>
To: emacs-devel@gnu.org
Subject: Re: git push precautions
Date: Wed, 28 Jan 2015 19:12:42 +0000 [thread overview]
Message-ID: <87bnlilnx1.fsf@violet.siamics.net> (raw)
In-Reply-To: <CAG-q9=YL+BkR7Jc4nxaq8o8V4ajNY8DCQCF7OZApnO=GdQTykw@mail.gmail.com> (Kelvin White's message of "Wed, 28 Jan 2015 18:57:49 +0000")
>>>>> Kelvin White <kwhite@gnu.org> writes:
>>>>> On Wed, Jan 28, 2015, 1:52 PM David Kastrup <dak@gnu.org> wrote:
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
>>>>> From: Ivan Shmakov Date: Wed, 28 Jan 2015 18:30:57 +0000
>>>> My preference is rather ‘push.default nothing’, so that
>>>> git-push(1) fails loudly should I fail to specify what to push.
>>> IMO (and IME) that's a nuisance that isn't justified.
>> git's defaults have historically been so unreasonable that I never
>> push without explicit mention of both local as well as target
>> reference. It decidedly is less of a nuisance than having to clean
>> up after Git goes overboard.
> I just use `git diff' before every push to see exactly what I'm
> pushing,
I’d generally use $ git log -p origin/branch branch instead, so
that I can review the individual changes, – as well as the
commit messages.
> and I always specify the remote repo i. e. `git push origin master'
So do I. And when one does, I’d say that that preference /is/
justified.
[…]
--
FSF associate member #7257 http://boycottsystemd.org/ … 3013 B6A0 230E 334A
next prev parent reply other threads:[~2015-01-28 19:12 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150128032211.21589.96959@vcs.savannah.gnu.org>
[not found] ` <E1YGJCm-0005dC-5P@vcs.savannah.gnu.org>
2015-01-28 3:32 ` master 7f4f16b: Merge branch 'master' of git.sv.gnu.org:/srv/git/emacs Lars Ingebrigtsen
2015-01-28 4:02 ` Lars Ingebrigtsen
2015-01-28 6:37 ` Paul Eggert
2015-01-28 6:45 ` Lars Ingebrigtsen
2015-01-28 7:16 ` Paul Eggert
2015-01-28 7:20 ` Lars Ingebrigtsen
2015-01-28 7:31 ` Lars Ingebrigtsen
2015-01-28 15:34 ` Eli Zaretskii
2015-01-28 15:45 ` Andreas Schwab
2015-01-28 16:32 ` Yuri Khan
2015-01-28 17:24 ` Eli Zaretskii
2015-01-28 17:39 ` Yuri Khan
2015-01-28 17:46 ` Eli Zaretskii
2015-01-28 17:53 ` Yuri Khan
2015-01-28 18:30 ` git push precautions Ivan Shmakov
2015-01-28 18:42 ` Eli Zaretskii
2015-01-28 18:52 ` David Kastrup
2015-01-28 18:57 ` Kelvin White
2015-01-28 19:12 ` Ivan Shmakov [this message]
2015-01-28 19:15 ` Eli Zaretskii
2015-01-28 19:34 ` David Kastrup
2015-01-29 5:39 ` Yuri Khan
2015-01-29 16:03 ` Eli Zaretskii
2015-01-29 17:47 ` Paul Eggert
2015-01-29 17:50 ` Eli Zaretskii
2015-01-29 17:57 ` Ivan Shmakov
2015-01-28 17:21 ` master 7f4f16b: Merge branch 'master' of git.sv.gnu.org:/srv/git/emacs Eli Zaretskii
2015-01-28 17:46 ` Andreas Schwab
2015-01-28 18:39 ` Eli Zaretskii
2015-01-28 19:07 ` git push precautions Ivan Shmakov
2015-01-29 9:07 ` master 7f4f16b: Merge branch 'master' of git.sv.gnu.org:/srv/git/emacs Andreas Schwab
2015-01-29 10:40 ` Nicolas Richard
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=87bnlilnx1.fsf@violet.siamics.net \
--to=ivan@siamics.net \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.