all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] master 2b316c0: ; * CONTRIBUTE: Add section about the bug tracker
Date: Fri, 6 Nov 2015 11:18:46 +0100	[thread overview]
Message-ID: <CAAeL0SS1XMVySUCzm9osi7j3aciNregUe8Pg+WvVtoyFakKpfQ@mail.gmail.com> (raw)
In-Reply-To: <837flvsaki.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1999 bytes --]

On Fri, Nov 6, 2015 at 11:10 AM, Eli Zaretskii <eliz@gnu.org> wrote:

> The idea of that passage is that merge is not to be afraid of.  That
> is correct with any modern dVCS.

This is inside a section about merging changes from the release branch to
the trunk. I wouldn't expect there a general discussion of merge, but of
merge policies in Emacs, and about gitmerge.el.

> I don't think so.

In this case, before codifying these policies we should agree on them,
shouldn't we?

In general (this is *not* a complain, just an impression), having been out
for a year, so I missed the switch to git, I think that for a newcomer, the
information about using git with Emacs is a bit scattered. We have sections
in CONTRIBUTE, we have admin/notes/repo, admin/notes/git-workflow, which
starts with the not-very-reassuring "(This is a draft.  The method here
won't actually work yet, because neither git-new-workdir nor
merge-changelog are in the Emacs distribution yet.)". And then we have two
different documents on EmacsWiki.

A trivial change for the obsolete references to Bazaar.

diff --git a/admin/notes/repo b/admin/notes/repo
index b27a3f4..d28955c 100644
--- a/admin/notes/repo
+++ b/admin/notes/repo
@@ -41,8 +41,8 @@ preferable not to merge from master until you are done
with the
 feature.  Unless you really need some change that was done on the
 master while you were developing on the branch, you don't really need
 those merges; just merge once, when you are done with the feature, and
-Bazaar will take care of the rest.  Bazaar is much better in this than
-CVS, so interim merges are unnecessary.
+Git will take care of the rest.  Git is much better in this than CVS
+or Bazaar, so interim merges are unnecessary.

 Or use shelves; or rebase; or do something else.  See the thread for
 yet another fun excursion into the exciting world of version control.
warning: LF will be replaced by CRLF in admin/notes/repo.
The file will have its original line endings in your working directory.

[-- Attachment #2: Type: text/html, Size: 2460 bytes --]

  reply	other threads:[~2015-11-06 10:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20151106085750.28172.54745@vcs.savannah.gnu.org>
     [not found] ` <E1ZucqE-0007L0-MZ@vcs.savannah.gnu.org>
2015-11-06  9:33   ` [Emacs-diffs] master 2b316c0: ; * CONTRIBUTE: Add section about the bug tracker Juanma Barranquero
2015-11-06  9:49     ` Eli Zaretskii
2015-11-06  9:56       ` Juanma Barranquero
2015-11-06 10:10         ` Eli Zaretskii
2015-11-06 10:18           ` Juanma Barranquero [this message]
2015-11-06 10:44             ` Eli Zaretskii
2015-11-06 13:59               ` Juanma Barranquero
2015-11-06 14:27                 ` Eli Zaretskii
2015-11-06 10:16         ` Use of git branches (was: [Emacs-diffs] master 2b316c0: ; * CONTRIBUTE: Add section about the bug tracker) Nicolas Richard
2015-11-06 10:46           ` Eli Zaretskii
2015-11-06 13:54             ` Juanma Barranquero
2015-11-06 14:56               ` Use of git branches David Kastrup
2015-11-07  1:57                 ` Juanma Barranquero
2015-11-07  8:18                   ` David Kastrup
2015-11-07  9:45                     ` Juanma Barranquero
2015-11-06 16:05               ` John Wiegley
2015-11-07  2:02                 ` Juanma Barranquero

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=CAAeL0SS1XMVySUCzm9osi7j3aciNregUe8Pg+WvVtoyFakKpfQ@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=eliz@gnu.org \
    --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.