From: Chris Marusich <cmmarusich@gmail.com>
To: Catonano <catonano@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: workflow
Date: Sat, 06 Jan 2018 14:17:13 -0800 [thread overview]
Message-ID: <877esur5sm.fsf@gmail.com> (raw)
In-Reply-To: <20180104101213.d4gcgqihxu6d77eb@abyayala> (ng0@n0.is's message of "Thu, 4 Jan 2018 10:12:13 +0000")
[-- Attachment #1: Type: text/plain, Size: 612 bytes --]
ng0 <ng0@n0.is> writes:
> You can stash those po/* files, it's the first thing I do if I ever
> happen to work on a complete new checkout.
Do you stash JUST the po files? I have often found these po files very
annoying while trying to make changes to Guix and test locally. I think
that if I do "git stash" and later "git stash pop", it updates the
timestamps of many files, so "make" rebuilds many, many things that it
really doesn't have to.
Beyond doing "git checkout po" are there any other ways to deal with
these po files that won't negate make's incremental build feature?
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-01-06 22:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 9:37 workflow Catonano
2018-01-04 9:46 ` workflow Catonano
2018-01-04 10:12 ` workflow ng0
2018-01-06 22:17 ` Chris Marusich [this message]
2018-01-06 22:56 ` workflow ng0
2018-01-04 10:13 ` workflow Hartmut Goebel
2018-01-04 11:30 ` workflow Catonano
2018-01-04 10:15 ` workflow Danny Milosavljevic
2018-01-04 11:31 ` workflow Catonano
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=877esur5sm.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=catonano@gmail.com \
--cc=guix-devel@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 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).