From: Andrea Corallo <acorallo@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
yandros@gmail.com, ofv@wanadoo.es, emacs-devel@gnu.org,
pipcet@protonmail.com
Subject: Re: scratch/igc as a feature branch [was: Re: igc: trying to chase a crash]
Date: Thu, 28 Nov 2024 10:43:45 -0500 [thread overview]
Message-ID: <yp1zfljgy8e.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m2jzcncyd1.fsf@gmail.com> ("Gerd Möllmann"'s message of "Thu, 28 Nov 2024 13:54:34 +0100")
Gerd Möllmann <gerd.moellmann@gmail.com> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Andrea Corallo <acorallo@gnu.org>
>>> Cc: gerd.moellmann@gmail.com, yandros@gmail.com, ofv@wanadoo.es,
>>> emacs-devel@gnu.org, pipcet@protonmail.com
>>> Date: Thu, 28 Nov 2024 05:56:29 -0500
>>>
>>> Eli Zaretskii <eliz@gnu.org> writes:
>>>
>>> > The question is indeed what kind of trouble this could cause. If it
>>> > loses the history, I wouldn't do it, since the fact that it's under
>>> > scratch/ is not a catastrophe, IMO.
>>>
>>> Sure, my idea would be to just push the current head of scratch/icg to
>>> feature/igc (and remove the first), so no history would be lost.
>>
>> If that works (I never did anything like that, so don't know what Git
>> does), then I don't mind.
>
> One can also rename branches, BTW.
Cool didn't know it 😀
>>
>> If we do this, it would be good to post a message here telling people
>> how to switch to the renamed branch, even if that is trivial.
>
> Shouldn't we wait for Pip to say something?
Sure
next prev parent reply other threads:[~2024-11-28 15:43 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 18:48 igc: trying to chase a crash Óscar Fuentes
2024-11-25 19:23 ` Eli Zaretskii
2024-11-25 19:53 ` Óscar Fuentes
2024-11-25 20:01 ` Eli Zaretskii
2024-11-25 20:51 ` Óscar Fuentes
2024-11-26 3:33 ` Eli Zaretskii
2024-11-26 5:17 ` Gerd Möllmann
2024-11-26 18:29 ` chad
2024-11-26 21:39 ` Andrea Corallo
2024-11-27 5:28 ` Gerd Möllmann
2024-11-27 7:50 ` Andrea Corallo
2024-11-27 7:55 ` Gerd Möllmann
2024-11-27 8:52 ` Andrea Corallo
2024-11-27 9:12 ` Gregor Zattler
2024-11-27 9:26 ` Andrea Corallo
2024-11-27 10:02 ` Gerd Möllmann
2024-11-27 10:25 ` icg build instructions [was: Re: igc: trying to chase a crash] Andrea Corallo
2024-11-27 11:12 ` Gerd Möllmann
2024-11-27 11:51 ` Óscar Fuentes
2024-11-27 14:23 ` Gerd Möllmann
2024-11-27 13:43 ` Andrea Corallo
2024-11-27 13:49 ` Andrea Corallo
2024-11-27 14:16 ` Gerd Möllmann
2024-11-28 12:46 ` Óscar Fuentes
2024-11-28 12:55 ` Gerd Möllmann
2024-11-28 13:00 ` Pip Cet via Emacs development discussions.
2024-11-28 14:10 ` Óscar Fuentes
2024-11-27 15:10 ` Eli Zaretskii
2024-11-28 4:42 ` Gerd Möllmann
2024-11-28 9:35 ` Eli Zaretskii
2024-11-27 10:40 ` igc: trying to chase a crash Vincenzo Pupillo
2024-11-27 10:44 ` Andrea Corallo
2024-11-27 10:59 ` Óscar Fuentes
2024-11-27 15:02 ` Andrea Corallo
2024-11-27 11:16 ` Gerd Möllmann
2024-11-27 13:47 ` Andrea Corallo
2024-11-27 14:48 ` Gerd Möllmann
2024-11-27 15:04 ` Óscar Fuentes
2024-11-27 12:37 ` Jeff Walsh
2024-11-27 15:11 ` Eli Zaretskii
2024-11-27 9:55 ` Gerd Möllmann
2024-11-27 10:01 ` Andrea Corallo
2024-11-27 10:08 ` Gerd Möllmann
2024-11-27 10:18 ` scratch/igc as a feature branch [was: Re: igc: trying to chase a crash] Andrea Corallo
2024-11-27 15:08 ` Eli Zaretskii
2024-11-28 10:56 ` Andrea Corallo
2024-11-28 11:59 ` Eli Zaretskii
2024-11-28 12:54 ` Gerd Möllmann
2024-11-28 12:57 ` Pip Cet via Emacs development discussions.
2024-11-28 13:12 ` Gerd Möllmann
2024-12-12 10:20 ` Andrea Corallo
2024-11-28 15:43 ` Andrea Corallo [this message]
2024-11-27 15:06 ` igc: trying to chase a crash Eli Zaretskii
2024-11-28 4:46 ` Gerd Möllmann
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=yp1zfljgy8e.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=ofv@wanadoo.es \
--cc=pipcet@protonmail.com \
--cc=yandros@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.