From: EuAndreh via <help-guix@gnu.org>
To: help-guix <Help-Guix@gnu.org>
Subject: Files not .gitignored when contributing to Guix
Date: Fri, 17 Jan 2020 15:57:56 -0300 [thread overview]
Message-ID: <8736cdewqz.fsf@euandre.org> (raw)
Hi Guix!
When running the setup steps to prepare a patch, I find myself with a
dirty repository of changed files. Is this expected behaviour?
I couldn't find guidance regarding that on the manual or the mailing
list archives (only a similar issue[0]), and I wonder if is there a way
to avoid it, or should I just get used to it? Is there something missing
for things being this way that I didn't get yet?
The output of make spits some warning regarding outdated .po files. If
the dirty files are generated, should they even be commited in the
repository if they are derived data? Looking at the diff, it confirms
this hypothesis: the diff of the .po files contain mostly generated
translation strings and timestamps.
The setup steps I use are:
--8<---------------cut here---------------start------------->8---
cd $GUIX_REPO
git clean -ffdx
guix environment guix --ad-hoc help2man git strace
./bootstrap
./configure --localstatedir=/var
make
--8<---------------cut here---------------end--------------->8---
At the end the dirty files are:
--8<---------------cut here---------------start------------->8---
$ git status
Sur la branche master
Modifications qui ne seront pas validées :
(utilisez "git add <fichier>..." pour mettre à jour ce qui sera validé)
(utilisez "git restore <fichier>..." pour annuler les modifications dans le répertoire de travail)
modifié : po/guix/cs.po
modifié : po/guix/da.po
modifié : po/guix/de.po
modifié : po/guix/eo.po
modifié : po/guix/es.po
modifié : po/guix/fr.po
modifié : po/guix/hu.po
modifié : po/guix/pl.po
modifié : po/guix/pt_BR.po
modifié : po/guix/sr.po
modifié : po/guix/sv.po
modifié : po/guix/vi.po
modifié : po/guix/zh_CN.po
modifié : po/packages/da.po
modifié : po/packages/de.po
modifié : po/packages/eo.po
modifié : po/packages/es.po
modifié : po/packages/fr.po
modifié : po/packages/hu.po
modifié : po/packages/pl.po
modifié : po/packages/pt_BR.po
modifié : po/packages/sr.po
modifié : po/packages/vi.po
modifié : po/packages/zh_CN.po
aucune modification n'a été ajoutée à la validation (utilisez "git add" ou "git commit -a")
--8<---------------cut here---------------end--------------->8---
I'm looking to a better way to handle this situation (that I find a bit
of a nuisance right now) or maybe just an explanation behind the way
things currently are.
Thanks :)
EuAndreh
[0]: https://lists.gnu.org/archive/html/guix-devel/2018-12/msg00387.html
next reply other threads:[~2020-01-17 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 18:57 EuAndreh via [this message]
2020-01-17 19:19 ` Files not .gitignored when contributing to Guix Julien Lepiller
2020-01-19 7:06 ` Efraim Flashner
2020-01-21 0:12 ` EuAndreh via
2020-01-21 0:05 ` EuAndreh via
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=8736cdewqz.fsf@euandre.org \
--to=help-guix@gnu.org \
--cc=eu@euandre.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.