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 19:52:40 +0200 [thread overview]
Message-ID: <87sg3zwdjr.fsf@elephly.net> (raw)
In-Reply-To: <d63078620a6317516cba22e6d579b1763294d6d7.camel@divoplade.fr>
divoplade <d@divoplade.fr> writes:
> Le vendredi 09 avril 2021 à 15:52 +0200, Ricardo Wurmus a écrit :
>> I’m saying that for public
>> channels it’s the wrong workflow as it results in rewritten history.
>
> My channels aren’t public (they are git repos on the file system), but
> I fail to understand how it makes a difference. Maybe the
> misunderstanding is in the term "rewritten history", which can refer to
> history (past releases of a package) or the git commit hierarchy? It’s
> important not to confuse them.
I’m talking about git commits.
“guix pull” fetches from channels, which are git repositories. When git
history is rewritten (e.g. with a rebase) it has no way of forwarding to
the new state.
Have you considered using a merge-based workflow for these channels?
Or, since these channels aren’t public, perhaps using GUIX_PACKAGE_PATH
would be more convenient?
--
Ricardo
prev parent reply other threads:[~2021-04-09 17: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
2021-04-09 15:40 ` divoplade
2021-04-09 17:52 ` Ricardo Wurmus [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
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=87sg3zwdjr.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).