unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Getting rid of "source file .. newer than compiled" messages
Date: Mon, 3 Apr 2017 16:09:41 +0200	[thread overview]
Message-ID: <58E257A5.1030705@crazy-compilers.com> (raw)
In-Reply-To: <idja8b9wlcy.fsf@bimsb-sys02.mdc-berlin.net>

Hi Ricardo,

Am 02.01.2017 um 16:08 schrieb Ricardo Wurmus:
> If you want to keep a stable branch of Guix around you can use “git
> worktree”.  Then you can have a worktree on master and another worktree
> where your WIP branches are being edited.  Editing or switching branches
> in one worktree won’t affect the other worktree.

I'm using this git worktree feature now since one or two weeks and this
is really great. I have several worktrees for different "projects" (like
updating KDE Frameworks).

Side-note: You tip also made me use worktrees for when generating a
github-pages-based website using sphinx: The _build/html directory is
the worktree holding the "gh-pages" branch. Works like a charm :-)
Details: https://github.com/pyinstaller/pyinstaller.github.io

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

  reply	other threads:[~2017-04-03 14:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-02 12:40 Getting rid of "source file .. newer than compiled" messages Hartmut Goebel
2017-01-02 13:23 ` Danny Milosavljevic
2017-01-02 13:28   ` Hartmut Goebel
2017-01-02 15:08     ` Ricardo Wurmus
2017-04-03 14:09       ` Hartmut Goebel [this message]
2017-01-02 13:30 ` David Craven
2017-01-02 15:36 ` John Darrington

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=58E257A5.1030705@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=guix-devel@gnu.org \
    --cc=ricardo.wurmus@mdc-berlin.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).