From: "Ludovic Courtès" <ludo@gnu.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: 31/31: DRAFT gnu: bootstrap: Add support for the Hurd.
Date: Sun, 15 Mar 2020 22:27:21 +0100 [thread overview]
Message-ID: <87pnddgvgm.fsf@gnu.org> (raw)
In-Reply-To: <87eetxrjtv.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Thu, 12 Mar 2020 10:41:48 +0100")
Hi!
Jan Nieuwenhuizen <janneke@gnu.org> skribis:
> FWIW, yes the rebuilds are annoying but I find managing/juggling
> different working setups especially cumbersome. A rebuild takes about a
> half a day round-trip time and during that I'm also doing development.
> I want to test smaller changes but am also making changes that will
> trigger another rebuild. Also, I don't want to lose my last working
> setup (VM+git). For that I'm creating many branches, tagged with
> numbers (wip-hurd0, wip-hurd-system3; etc), which "works" but... Just
> wondering how you all handle this kind of thing.
I use git worktrees.
Now, I think the main limitation is mind availability. For some reason,
earlier during Guix development, I’d manage to do core-updates testing
in parallel with unrelated things on master. Nowadays, I find it harder
to be on more than one front at a time. Maybe I just got older? :-)
Perhaps one way to reduce the burden is to work on smaller, more focused
changes. Perhaps “GNU/Hurd support” is too broad a topic for a branch
and you could instead target intermediate milestones? At least that
would more often give a feeling of achievement, which I find important
to stay motivated.
My 2¢…
Ludo’.
prev parent reply other threads:[~2020-03-15 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200312065852.10633.59398@vcs0.savannah.gnu.org>
[not found] ` <20200312065911.D981520B7E@vcs0.savannah.gnu.org>
2020-03-12 9:04 ` 31/31: DRAFT gnu: bootstrap: Add support for the Hurd Ludovic Courtès
2020-03-12 9:41 ` Jan Nieuwenhuizen
2020-03-15 18:23 ` Jan Nieuwenhuizen
2020-03-16 7:42 ` bug#40006: " Efraim Flashner
2020-03-15 18:23 ` Jan Nieuwenhuizen
2020-03-15 21:27 ` Ludovic Courtès [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnddgvgm.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=janneke@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.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.