From: David Kastrup <dak@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Nicolas Richard <youngfrog@members.fsf.org>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Use of git branches
Date: Fri, 06 Nov 2015 15:56:23 +0100 [thread overview]
Message-ID: <87twozrxbc.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAAeL0SQjqXhE9M=TLnWW01Gq8hvfVmk7r70Ex+BBV7rVB20Omw@mail.gmail.com> (Juanma Barranquero's message of "Fri, 6 Nov 2015 14:54:58 +0100")
Juanma Barranquero <lekktu@gmail.com> writes:
> Ok, we have a new thread (thanks, Nicolas).
>
> Could we use it to clarify what's the policy on public branches on the repo
> (or, in general, our nettiquete wrt the emacs repo)? (So we can document
> it.)
>
> One thing that I dislike is having 66 branches in git branch -r, of which
> 41 are definitely obsolete (other-branches/* and old-branches/* are, except
> for cairo, between 3 and 18 years old)
git branch --contains master~100
does a pretty good job of weeding out inactive branches.
--
David Kastrup
next prev parent reply other threads:[~2015-11-06 14:56 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
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 ` David Kastrup [this message]
2015-11-07 1:57 ` Use of git branches 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=87twozrxbc.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=youngfrog@members.fsf.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.