From: Samuel Wales <samologist@gmail.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: git branch rename and git config q
Date: Mon, 6 Jun 2022 20:33:35 -0700 [thread overview]
Message-ID: <CAJcAo8vpc7Pn8PP9xV=NUj5LC=s98hD12Mw+zzGdHFtdKn7jXg@mail.gmail.com> (raw)
In-Reply-To: <t7l9kc$so1$1@ciao.gmane.io>
thanks for the links [my brain is not up to understanding atm]. when
you say perhaps i do not need to rename branches, do you mean that my
guess at a solution had a redundant step? and that step was manually
edit config file? no need there?
the last par of your email makes it seem as if i should do a git
[interactive?] rebase operation from [top of] local on bugfix, even
though it is already rebasing on maint each upgrade. would that be a
good description of what you meant?
On 6/6/22, Max Nikulin <manikulin@gmail.com> wrote:
> On 06/06/2022 11:13, Samuel Wales wrote:
>>
>> i have a repo where i have patches that i carry along i a local
>> branch. these are rebased automagically when i upgrade org.
>
> You may change remote for this repository. Perhaps you do not need to
> rename branches.
> https://list.orgmode.org/sj91nb$d9j$1@ciao.gmane.io/
>
> https://git-scm.com/book/en/v2
>
>
>
--
The Kafka Pandemic
A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com
next prev parent reply other threads:[~2022-06-07 3:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 4:13 git branch rename and git config q Samuel Wales
2022-06-06 16:22 ` Max Nikulin
2022-06-07 3:33 ` Samuel Wales [this message]
2022-06-07 15:24 ` Max Nikulin
2022-06-07 23:35 ` Samuel Wales
2022-06-08 2:10 ` Ihor Radchenko
2022-06-08 16:20 ` Max Nikulin
2022-06-08 20:50 ` Tim Cross
2022-06-09 0:09 ` Samuel Wales
2022-06-09 0:16 ` Samuel Wales
2022-06-09 0:23 ` Samuel Wales
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJcAo8vpc7Pn8PP9xV=NUj5LC=s98hD12Mw+zzGdHFtdKn7jXg@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).