From: John Soo <jsoo1@asu.edu>
To: Arne Babenhauserheide <arne_bab@web.de>
Cc: 41604@debbugs.gnu.org
Subject: bug#41604: guix pull impossible after rebasing a local repository
Date: Sat, 30 May 2020 22:04:27 -0700 [thread overview]
Message-ID: <1D37F750-2DA3-4DF1-91A5-92637E58E753@asu.edu> (raw)
In-Reply-To: <87tuzxgzw2.fsf@web.de>
Hi Arne,
Interesting idea about mercurial.
My problem largely comes from the fact that I specified a branch in channels.scm for over a year with the same workflow. If a branch can be specified for a channel repo then the system probably should handle the current pull commit not being available in the history.
The commit history authentication is nice but seems to have regressed this particular use case.
- John
next prev parent reply other threads:[~2020-05-31 5:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 16:38 bug#41604: guix pull impossible after rebasing a local repository John Soo
[not found] ` <handler.41604.B.159077032116756.ack@debbugs.gnu.org>
2020-05-29 16:41 ` bug#41604: Acknowledgement (guix pull impossible after rebasing a local repository) John Soo
2020-05-29 16:52 ` bug#41604: guix pull impossible after rebasing a local repository zimoun
2020-05-29 17:10 ` John Soo
2020-05-29 17:44 ` zimoun
2020-05-29 18:22 ` John Soo
2020-05-29 18:39 ` zimoun
2020-05-30 2:26 ` John Soo
2020-05-30 10:45 ` zimoun
2020-05-30 16:18 ` Arne Babenhauserheide
2020-05-31 5:04 ` John Soo [this message]
2020-06-01 16:48 ` zimoun
2020-06-01 17:28 ` John Soo
2020-06-01 16:35 ` zimoun
2020-06-03 9:28 ` Ludovic Courtès
2020-06-03 13:44 ` John Soo
2020-06-03 15:13 ` Ludovic Courtès
2020-06-04 14:11 ` John Soo
2020-06-05 1:44 ` zimoun
2020-06-05 16:13 ` Ludovic Courtès
2020-06-05 1:23 ` zimoun
2020-06-05 16:17 ` Ludovic Courtès
2020-06-05 17:51 ` zimoun
2020-06-07 21:16 ` Ludovic Courtès
2020-06-07 22:25 ` zimoun
2020-06-07 23:52 ` John Soo
2020-06-10 14:51 ` Ludovic Courtès
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=1D37F750-2DA3-4DF1-91A5-92637E58E753@asu.edu \
--to=jsoo1@asu.edu \
--cc=41604@debbugs.gnu.org \
--cc=arne_bab@web.de \
/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/guix.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).