unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Having a custom merge process
Date: Sat, 26 Dec 2015 11:47:58 +0200	[thread overview]
Message-ID: <8360zlk0c1.fsf@gnu.org> (raw)
In-Reply-To: <87poxunllj.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat,  26 Dec 2015 00:40:24 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sat, 26 Dec 2015 00:40:24 +0100
> 
> John Wiegley <jwiegley@gmail.com> writes:
> 
> > I've used Git in many scenarios, on many projects, but some of the practices
> > we're using here for Emacs development I've never seen before. This simply
> > makes me wonder how much of that difference is truly necessary, or is a result
> > of having evolved to this point from CVS and then Bazaar.
> 
> I think the latter is probably true.  There are many people here who
> aren't that fond of git.  (I'm one of them.  :-))  And that's probably
> somewhat unusual, these days.

But the merge policies and what gitmerge.el does (and bzrmerge.el did
before it) were defined by people who are neither non-lovers of Git
nor are prisoners of the CVS-like way of thinking.  Those policies are
determined by the project needs first and foremost, not by what the
tools can or cannot do well.

So I don't see how this conclusion could be right.

But again, without having a list of "surprising" practices, it's hard
to reason about this.

> Hey!  It's time for a new 500+ article VC thread!

Yes.  Long time no seen.



  parent reply	other threads:[~2015-12-26  9:47 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
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 [this message]
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=8360zlk0c1.fsf@gnu.org \
    --to=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).