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

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Fri, 6 Nov 2015 10:33:48 +0100
> 
> Speaking of admin/notes/repo... It has a few obsolete references to Bazaar, and
> a comment "[The section on git merge procedure has not yet been written.]"

Clean up is welcome.

> And I miss some discussion about policies on pushing branches to the repo.
> old-branches/* and other-branches/* are ancient, but what about the others?
> Some are prefixed with scratch/ or fix/ (one case), while others are not (like
> nsm, stream or shr-fontified). Is there any rhyme or reason?

The convention was to use scratch/ for experimental branches and fix/
for public feature branches that fix some issue.  Suggestions to
codify this are welcome.

> Also, perhaps some of the non-prefixed branches are really ancient,
> like pending, and should be renamed?

No idea, but I think this was already examined at some point, and what
you see is the result.

Thanks.



  reply	other threads:[~2015-11-06  9:49 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 [this message]
2015-11-06  9:56       ` Juanma Barranquero
2015-11-06 10:10         ` Eli Zaretskii
2015-11-06 10:18           ` Juanma Barranquero
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=83bnb7sbiz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    /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.