unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Wiegley <jwiegley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, dak@gnu.org, emacs-devel@gnu.org
Subject: Re: EWW bugs should be fixed on emacs-25 branch
Date: Fri, 25 Dec 2015 12:09:10 -0800	[thread overview]
Message-ID: <m2k2o2i93t.fsf@newartisans.com> (raw)
In-Reply-To: <83y4cijo24.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 25 Dec 2015 22:00:51 +0200")

>>>>> Eli Zaretskii <eliz@gnu.org> writes:

> Maybe so, but better be safe than sorry. Given the number of times I saw Git
> experts here make mistakes about what does and doesn't work, I will trust
> gitmerge.el and our experience more than I trust what we think we know about
> Git. Also, gitmerge.el should DTRT no matter which version of Git is
> installed (I hear that some systems still have Git 1.7.1 or something like
> that).

I suppose then that I would like to understand exactly what gitmerge.el is
adding to the picture. I've managed some pretty crazy merge scenarios as a
contractor, and it never required building custom merging tools before.

So we run the opposite risk of people "just using gitmerge.el", but not
understanding what is actually happening. If it works for you, that's great;
but if I properly understand what is being done, then I can find a workflow
that might suit me better.

-- 
John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2



  reply	other threads:[~2015-12-25 20:09 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-25  7:52 EWW bugs should be fixed on emacs-25 branch Eli Zaretskii
2015-12-25  8:06 ` Eli Zaretskii
2015-12-25  8:26   ` David Kastrup
2015-12-25 14:18     ` Eli Zaretskii
2015-12-25 16:58       ` John Wiegley
2015-12-25 17:15         ` Eli Zaretskii
2015-12-25 17:23           ` John Wiegley
2015-12-25 19:41             ` Eli Zaretskii
2015-12-25 19:55               ` John Wiegley
2015-12-25 20:00                 ` Eli Zaretskii
2015-12-25 20:09                   ` John Wiegley [this message]
2015-12-25 20:40                     ` Eli Zaretskii
2015-12-25 20:44                       ` John Wiegley
2015-12-25 20:48                         ` Eli Zaretskii
2015-12-25 20:53                           ` John Wiegley
2015-12-25 23:18                         ` David Engster
2015-12-25 23:35                           ` Having a custom merge process (was: EWW bugs should be fixed on emacs-25 branch) John Wiegley
2015-12-25 23:40                             ` Having a custom merge process Lars Ingebrigtsen
2015-12-25 23:59                               ` David Engster
2015-12-26  0:47                                 ` John Wiegley
2015-12-26  7:35                                 ` Paul Eggert
2015-12-26  9:47                               ` Eli Zaretskii
2015-12-26  9:44                             ` Having a custom merge process (was: EWW bugs should be fixed on emacs-25 branch) Eli Zaretskii
2015-12-26 17:00                               ` EWW To Elpa? Re: Having a custom merge process raman
2015-12-26 17:51                                 ` Lars Ingebrigtsen
2015-12-26 21:06                                   ` Artur Malabarba
2015-12-28 21:17                                     ` John Wiegley
2015-12-26 18:40                                 ` Artur Malabarba
2015-12-27 16:29                                   ` raman
2015-12-27  2:52                               ` Having a custom merge process (was: EWW bugs should be fixed on emacs-25 branch) Richard Stallman
2015-12-27  3:49                                 ` Eli Zaretskii
2015-12-25 16:07 ` EWW bugs should be fixed on emacs-25 branch Lars Ingebrigtsen
2015-12-25 16:21   ` Eli Zaretskii

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=m2k2o2i93t.fsf@newartisans.com \
    --to=jwiegley@gmail.com \
    --cc=dak@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 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).