From: John Kacur <jkacur@redhat.com>
To: Josh Cartwright <josh.cartwright@ni.com>
Cc: Clark Williams <williams@redhat.com>,
John Kacur <jkacur@redhat.com>,
linux-rt-users@vger.kernel.org
Subject: Re: [PATCH rt-tests] gitignore: add librttest.a to git ignore
Date: Thu, 18 Oct 2012 12:32:19 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.02.1210181229470.5341@tycho> (raw)
In-Reply-To: <20121018162359.GA27911@beefymiracle.amer.corp.natinst.com>
On Thu, 18 Oct 2012, Josh Cartwright wrote:
> Commit fb7ef61416b6b191a5186a715e51792847de883c introduced librttest.a
> as a library, but did not add it to .gitignore. Add it now.
>
> Signed-off-by: Josh Cartwright <josh.cartwright@ni.com>
> ---
> .gitignore | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/.gitignore b/.gitignore
> index 047925c..f7ba1d0 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -27,6 +27,7 @@ SRPMS
> /pip_stress
> /hackbench
> /pmqtest
> +librttest.a
>
> rt-tests.spec
> tags
> --
> 1.7.12.3
> --
Oh, thanks, but I already have the following queued up for the next
release
commit d63f567c646e07da87d9ce3cce5e5add74c97e16
Author: John Kacur <jkacur@redhat.com>
Date: Wed May 9 17:32:11 2012 +0200
rt-tests / gitignore: Exclude patches and .a libs too.
Minor fix to make working with git nicer.
Now that we're building a lib, we need to exclude it from git status output.
Do the same for patches we generate or apply.
Signed-off-by: John Kacur <jkacur@redhat.com>
diff --git a/.gitignore b/.gitignore
index 047925c..1924e73 100644
--- a/.gitignore
+++ b/.gitignore
@@ -3,6 +3,8 @@
*.o
*.tar.gz
*.d
+*.patch
+*.a
tmp
patches
ChangeLog
next prev parent reply other threads:[~2012-10-18 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 16:23 [PATCH rt-tests] gitignore: add librttest.a to git ignore Josh Cartwright
2012-10-18 16:32 ` John Kacur [this message]
2012-10-18 17:13 ` Josh Cartwright
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=alpine.LFD.2.02.1210181229470.5341@tycho \
--to=jkacur@redhat.com \
--cc=josh.cartwright@ni.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.com \
/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