From: Mats Liljegren <liljegren.mats2@gmail.com>
To: Linux Test Project General Discussions <ltp-list@lists.sourceforge.net>
Subject: [LTP] Versioned files modified by build
Date: Thu, 13 Mar 2014 11:25:07 +0100 [thread overview]
Message-ID: <53218783.6020200@gmail.com> (raw)
After building in-tree (GIT), I get the following when issuing "git
status" command:
# On branch master
# Changes not staged for commit:
# (use "git add <file>..." to update what will be committed)
# (use "git checkout -- <file>..." to discard changes in working
directory)
#
# modified: utils/ffsb-6.0-rc2/config.h.in
# modified: utils/ffsb-6.0-rc2/configure
#
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# testcases/kernel/io/stress_floppy/1000K_file
# testcases/kernel/io/stress_floppy/100K_file
# testcases/kernel/io/stress_floppy/10K_file
# testcases/kernel/io/stress_floppy/dumpdir/
This would suggest that the files utils/ffsb-6.0-rc2/config.h.in and
utils/ffsb-6.0-rc2/configure are version controlled. Are they supposed to?
Should above untracked files be added to .gitignore?
Or am I supposed to build somewhere else?
Regards
Mats Liljegren
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2014-03-13 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 10:25 Mats Liljegren [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-13 10:26 [LTP] Versioned files modified by build Mats Liljegren
2014-03-13 12:34 ` chrubis
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=53218783.6020200@gmail.com \
--to=liljegren.mats2@gmail.com \
--cc=ltp-list@lists.sourceforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox