From: Eli Zaretskii <eliz@gnu.org>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: emacs-devel@gnu.org
Subject: Re: Branches are Scary
Date: Fri, 18 Dec 2015 09:20:43 +0200 [thread overview]
Message-ID: <83mvt8xlx0.fsf@gnu.org> (raw)
In-Reply-To: <87bn9oydgw.fsf@russet.org.uk> (phillip.lord@russet.org.uk)
> From: phillip.lord@russet.org.uk (Phillip Lord)
> Date: Thu, 17 Dec 2015 21:25:35 +0000
>
> I was wondering if anyone could describe the git setup wrt to branches
> on the main Emacs git.
There's no setup I could think of. There are official branches where
development of to-be-released versions is going on, and there are all
the other branches people push to let others try experimental
features.
> I always find deleting branches (that I have created) rather an unhappy
> experience, as I worry that I will do the wrong thing, and accidentally
> delete emacs-25.
If you are afraid of deleting branches, don't. Someone else will come
and do it eventually.
> At the same time, if I am understanding things correctly, I can't squash
> and force feature and fix branches that I have pushed up, which means
> that these have to get deleted unmerged cause I squash and merge locally.
Public branches are public branches; don't do there anything that will
cause pain to people who might track them.
> Perhaps I am worried about this unnecessarily. Can I delete emacs-25 or
> master by mistake? And, at the same time, is it possible to squash
> things in other branches?
I suggest to refrain from squashing on public branches. Why do you
need it?
prev parent reply other threads:[~2015-12-18 7:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 21:25 Branches are Scary Phillip Lord
2015-12-17 21:49 ` Ingo Lohmar
2015-12-17 22:20 ` Phillip Lord
2015-12-17 23:35 ` John Wiegley
2015-12-18 7:28 ` Eli Zaretskii
2015-12-18 7:49 ` Yuri Khan
2015-12-18 9:05 ` Eli Zaretskii
2015-12-18 10:43 ` Phillip Lord
2015-12-18 15:48 ` Random832
2015-12-18 16:10 ` Eli Zaretskii
2015-12-18 16:46 ` Phillip Lord
2015-12-18 7:20 ` Eli Zaretskii [this message]
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=83mvt8xlx0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=phillip.lord@russet.org.uk \
/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.