From: Ricardo Wurmus <rekado@elephly.net>
To: divoplade <d@divoplade.fr>
Cc: help-guix@gnu.org
Subject: Re: Frequently-rebased channels
Date: Fri, 09 Apr 2021 15:52:11 +0200 [thread overview]
Message-ID: <87y2drwook.fsf@elephly.net> (raw)
In-Reply-To: <a060ebd61b4953eed9a2bd693d332f375d4a2891.camel@divoplade.fr>
divoplade <d@divoplade.fr> writes:
> Hello,
>
> Le vendredi 09 avril 2021 à 14:21 +0200, Ricardo Wurmus a écrit :
>> > I have a couple of channels that get rebased constantly.
>>
>> This seems like a broken workflow. Why would they be rebased
>> constantly, which results in rewritten history?
>
> Sorry, I don’t know how to respond to that. Of course, rebasing is
> essential with git, precisely because it results in rewritten commit
> history. The opposite (never rebasing) would be a broken workflow.
I’m not saying that rebasing is bad. I’m saying that for public
channels it’s the wrong workflow as it results in rewritten history.
--
Ricardo
next prev parent reply other threads:[~2021-04-09 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 12:06 Frequently-rebased channels divoplade
2021-04-09 12:21 ` Ricardo Wurmus
2021-04-09 12:57 ` divoplade
2021-04-09 13:52 ` Ricardo Wurmus [this message]
2021-04-09 15:40 ` divoplade
2021-04-09 17:52 ` Ricardo Wurmus
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2drwook.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=d@divoplade.fr \
--cc=help-guix@gnu.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.
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).