From: phillip.lord@russet.org.uk (Phillip Lord)
To: Ingo Lohmar <i.lohmar@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Branches are Scary
Date: Thu, 17 Dec 2015 22:20:06 +0000 [thread overview]
Message-ID: <8737v0yay1.fsf@russet.org.uk> (raw)
In-Reply-To: <874mfgn3t7.fsf@acer.localhost.com> (Ingo Lohmar's message of "Thu, 17 Dec 2015 22:49:40 +0100")
Ingo Lohmar <i.lohmar@gmail.com> writes:
>> 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 only delete local branches, that should not happen without your
> explicit consent (unless you are using a fairly malicious interface on
> top of plain git).
I'm using magit. I don't know what will happen if I try, and obvious, I
don't want to try.
>> 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.
>
> It seems that *this* is the actual problem to solve. The rule of thumb
> is simple: Do not squash or rebase any commits you have pushed out, it
> makes life hard for everybody else, that's why it's not allowed in the
> repository. If you still plan substantial cleanup of your commits, just
> do not push them yet.
Makes it hard to get comments on them, I think. I had substantial
comments on one branch (couldn't have completed it without them) as well
as an effective code review before I merged. Possibly, the solution is
not to use the main emacs git for this form of collaboration, but to
publish my own repo, but this seems an obvious use to me.
Clearly rebasing on a branch with many people are working on would be
bad.
> I am also unsure whether force-deleting branches in the emacs repo is
> permitted, but it does not matter: Please do not try to work around the
> restrictions by deleting branches.
I'm not. Just trying to clean up after myself.
>
>>
>> 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?
>>
>> Phil
>
> The concept of squashing is fairly unrelated to the concept of branches.
> The rules are the same for all commits, wherever they are.
Then I have learned something. Probably I can delete emacs-25 if I want.
Ah, well, I will just have to be careful.
Phil
next prev parent reply other threads:[~2015-12-17 22: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 [this message]
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
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=8737v0yay1.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=emacs-devel@gnu.org \
--cc=i.lohmar@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.