From: "Marc-André Lureau" <marcandre.lureau@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] .gitignore: remove vscclient
Date: Mon, 6 Nov 2017 14:30:56 -0500 (EST) [thread overview]
Message-ID: <1152775610.36873329.1509996656951.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <ae73f31f-749a-e02e-d04b-1090e350619e@redhat.com>
----- Original Message -----
> On 11/06/2017 12:54 PM, Marc-André Lureau wrote:
> > It was removed with libcacard.
>
> which was back in which commit? I'm trying to get an idea of how long
> this entry has been stale.
Since:
commit 7b02f5447c64d1854468f758398c9f6fe9e5721f
Author: Marc-André Lureau <marcandre.lureau@redhat.com>
Date: Sun Aug 30 11:48:40 2015 +0200
libcacard: use the standalone project
>
> I'm not opposed to this patch, but I personally like to leave .gitignore
> entries in place for several releases after they are last useful, to
> make incremental builds easier when jumping around between old and new
> branches across the point where the file was removed (as long as the new
> branch still ignores the file, then building the file in the old branch
> doesn't hurt the new branch). Of course, if I'm that involved in
> backporting madness across branches, I'm also fine updating my own
> .git/info/exclude for cruft that is built in only one of two branches,
> rather than relying on per-branch .gitignore to do it for me.
>
> --
> Eric Blake, Principal Software Engineer
> Red Hat, Inc. +1-919-301-3266
> Virtualization: qemu.org | libvirt.org
>
>
next prev parent reply other threads:[~2017-11-06 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 18:54 [Qemu-devel] [PATCH] .gitignore: remove vscclient Marc-André Lureau
2017-11-06 19:21 ` Eric Blake
2017-11-06 19:30 ` Marc-André Lureau [this message]
2017-11-06 19:55 ` Eric Blake
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=1152775610.36873329.1509996656951.JavaMail.zimbra@redhat.com \
--to=marcandre.lureau@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-devel@nongnu.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.
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 NNTP newsgroup(s).