all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "Fabián Ezequiel Gallina" <fgallina@gnu.org>, emacs-devel@gnu.org
Subject: Re: master 7f4f16b: Merge branch 'master' of git.sv.gnu.org:/srv/git/emacs
Date: Tue, 27 Jan 2015 23:16:02 -0800	[thread overview]
Message-ID: <54C88CB2.1030608@cs.ucla.edu> (raw)
In-Reply-To: <87twzbv1x0.fsf@building.gnus.org>

Lars Ingebrigtsen wrote:
> How did that happen?  I thought I was in either the master branch, or
> the shr-fontified branch.  I didn't try to do anything with the emacs-24
> branch...

Oh, sorry, I guess I misinterpreted the logs and Fabián did the merges 
(actually, merges) at about the same time?  But your name is on one of the 
master-installed merges as the committer, so I'm puzzled.  Whatever.  Anyway, 
the merges had quite a few conflicts that were resolved incorrectly.

Did anything leak into the master that you didn't want?  The nnimap `never' 
expiration fix, say?  (Commit 0cdd599c54aeda36e7e0696b2f90d2c286153a1d.)  Or the 
shr-make-table-1 patches (commits 1a369fc7f1ccec6954344ec1ee0211a4d24c312d and 
776705f49c5cb4e66c7dcb316fe499aa6a183888)?  If so, now might be a good time to 
revert these.

As a general rule, by the way, I almost never do anything other than "git pull" 
when I'm in my working copy of the Emacs master.  To do any real work, I clone 
that copy and work in some temporary branch in that clone.  Eventually when I 
have a patch I'm happy with, I use "git format-patch" to create a patch file, 
review the patch file, and then finally go to my copy of the master and publish 
the patch via "git am PATCHFILE; git push".  This lessens the likelihood of my 
inadvertently pushing something to savannah's master.



  reply	other threads:[~2015-01-28  7:16 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 [this message]
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
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=54C88CB2.1030608@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=fgallina@gnu.org \
    --cc=larsi@gnus.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.