all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Nils Gillmann <niasterisk@grrlz.net>
Cc: help-guix@gnu.org
Subject: Re: developing for guix with git
Date: Mon, 01 Feb 2016 00:49:09 +0100	[thread overview]
Message-ID: <87y4b5ia2y.fsf@elephly.net> (raw)
In-Reply-To: <878u35bscu.fsf@grrlz.net>


Nils Gillmann <niasterisk@grrlz.net> writes:

> Do you happen to know why guix in the situation I described,
> being on an up to date branch following master refuses to build,
> but once I switch to master branch, make clean, make clean-go (or
> go-clean?) and run make (and the other commands) again it builds
> successfully? This was my initial confusion.

It’s hard to say without being able to take a look at the state of the
branch.  It is possible that a change you introduced in your branch
broke things.  Maybe you could share error messages?

> I might have a thing or 2 to learn about rebasing and branching, but in
> theory from what I know it shouldn't really matter which branch I am
> on unless something's corrupted or broken.

I think of a branch as a pointer to a some commit in the graph.
Rebasing takes a range of commits and applies the changes they introduce
on top of some other commit.

When things suddenly break after rebasing the reason is usually in of
two categories:

* one of your (now relocated) commits broke something

* after rebasing, master commits that have been added since you first
  committed your changes are now part of the history of your commits —
  maybe these commits altered assumptions that were still valid when you
  first committed your changes.  An example for this is when a variable
  was renamed or moved in a master commit and your commits still use the
  old name.

Sharing some error output with us might help us identify what’s going on
in your case.  In any case, you could try bisecting your changes (divide
the set of your commits in half, and see if things are broken at that
commit; then recurse until you find the commit that introduced the cause
for the failure).  This works best when you made many small commits.

I’m using multiple branches for things that take me too long.  For most
developments, however, I’m working in a local “wip” branch, which is
regularly and in short intervals rebased onto master.

~~ Ricardo

  reply	other threads:[~2016-01-31 23:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 11:31 developing for guix with git Ni* Gillmann
2016-01-28 20:29 ` Efraim Flashner
2016-01-31 16:56   ` Nils Gillmann
2016-01-31 23:49     ` Ricardo Wurmus [this message]
2016-02-02 21:28       ` Nils Gillmann
2016-02-02 23:56         ` Leo Famulari
2016-02-03  0:51           ` Nils Gillmann
2016-02-03  6:58             ` Ricardo Wurmus
2016-02-03 11:24               ` Nils Gillmann
2016-02-03 12:00               ` Nils Gillmann
2016-02-03  0:46         ` Nils Gillmann

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=87y4b5ia2y.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    --cc=niasterisk@grrlz.net \
    /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.