unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: bruce.connor.am@gmail.com
Cc: handa@gnu.org, emacs-devel@gnu.org, emacs-diffs@gnu.org
Subject: Re: master 94ed516 2/4: Merge branch 'master' of	git.sv.gnu.org:/srv/git/emacs
Date: Tue, 06 Oct 2015 20:25:18 +0300	[thread overview]
Message-ID: <8337xnykn5.fsf@gnu.org> (raw)
In-Reply-To: <CAAdUY-La+=zFRyRmCBH8WSPr5xyfcozG_Brp3JjBDV2nfiPs-A@mail.gmail.com>

> Date: Tue, 6 Oct 2015 18:01:18 +0100
> From: Artur Malabarba <bruce.connor.am@gmail.com>
> Cc: Kenichi Handa <handa@gnu.org>, emacs-diffs@gnu.org,
> 	emacs-devel <emacs-devel@gnu.org>
> 
> Doing your work on a separate dev branch (and pulling master before
> merging dev onto master) is an important piece of git workflow.

AFAIU, it all depends on the workflow.  We indeed prefer it that way,
but I understand it's on no way a universal rule.

> Perhaps we ought to document that in the same place we teach people
> to clone the repo?

We already explain this in CONTRIBUTE.


  reply	other threads:[~2015-10-06 17:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20151005140014.24070.46905@vcs.savannah.gnu.org>
     [not found] ` <E1Zj6JL-0006Qd-Ij@vcs.savannah.gnu.org>
2015-10-06  9:18   ` master 94ed516 2/4: Merge branch 'master' of git.sv.gnu.org:/srv/git/emacs Artur Malabarba
2015-10-06 14:09     ` Kaushal Modi
2015-10-06 14:47       ` [Emacs-diffs] " Alan Mackenzie
2015-10-06 14:47       ` Óscar Fuentes
2015-10-06 14:59         ` Kaushal Modi
2015-10-06 15:48           ` David Kastrup
2015-10-06 16:20     ` [Emacs-diffs] " Stefan Monnier
2015-10-06 17:01       ` Artur Malabarba
2015-10-06 17:25         ` Eli Zaretskii [this message]
2015-10-06 20:55           ` Artur Malabarba
2015-10-07 15:06             ` [Emacs-diffs] " 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=8337xnykn5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bruce.connor.am@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-diffs@gnu.org \
    --cc=handa@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 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).