From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@suse.de>
Cc: fgallina@gnu.org, larsi@gnus.org, eggert@cs.ucla.edu,
emacs-devel@gnu.org
Subject: Re: master 7f4f16b: Merge branch 'master' of git.sv.gnu.org:/srv/git/emacs
Date: Wed, 28 Jan 2015 20:39:52 +0200 [thread overview]
Message-ID: <83d25yoikn.fsf@gnu.org> (raw)
In-Reply-To: <87386u3iir.fsf@igel.home>
> From: Andreas Schwab <schwab@suse.de>
> Cc: fgallina@gnu.org, larsi@gnus.org, eggert@cs.ucla.edu, emacs-devel@gnu.org
> Date: Wed, 28 Jan 2015 18:46:36 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Andreas Schwab <schwab@suse.de>
> >> Cc: Lars Ingebrigtsen <larsi@gnus.org>, fgallina@gnu.org, eggert@cs.ucla.edu, emacs-devel@gnu.org
> >> Date: Wed, 28 Jan 2015 16:45:59 +0100
> >>
> >> > Why not "git show"?
> >>
> >> Because that doesn't tell you what will be pushed.
> >
> > I think it does, if I'm careful to push each commit.
>
> Why taking chances when it's easy to avoid?
OK, but is "push -n" really the best alternative? How about
"git diff origin/master" (resp. origin/emacs-24)?
next prev parent reply other threads:[~2015-01-28 18:39 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83d25yoikn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=fgallina@gnu.org \
--cc=larsi@gnus.org \
--cc=schwab@suse.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).