From: Ian Campbell <ian.campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [OSSTEST PATCH] build_clone: git clean newly cloned trees
Date: Mon, 2 Nov 2015 14:19:17 +0000 [thread overview]
Message-ID: <1446473957.3088.48.camel@citrix.com> (raw)
In-Reply-To: <563242C0.4040701@citrix.com>
On Thu, 2015-10-29 at 16:01 +0000, Andrew Cooper wrote:
> On 29/10/15 15:57, Ian Jackson wrote:
> > This may seem redundant, however:
> >
> > git does not track empty directories. So it can happen that a
> > directory is created as part of `git clone', but is empty in the
> > revision switched to with `git checkout'.
> >
> > In this situation, the tree we are going to build ought not to contain
> > this directory, because that directory will not (in general) be
> > produced, eg when the revision being switched to becomes master.
> >
> > We can use git clean to produce a working tree whose contents -
> > including the presence or absence of empty directories - depends only
> > on the commit we are trying to check out, and not on the previous
> > states of the git history or working tree.
> >
> > For example, if a directory is made empty (ie, deleted, since git does
> > not distinguish) in xen.git#staging, osstest's clones of
> > xen.git#master will produce the directory, but `git checkout' of
> > staging won't delete it. If the xen.git build system mistakenly
> > depends on this directory, we won't detect this until the deletion
> > reaches master. This situation actually occurred with xen.git#598e97f
> > "tools/python: remove broken xl binding" (fixed in b261366f).
> >
> > Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
> > CC: Andrew Cooper <andrew.cooper3@citrix.com>
>
> Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
prev parent reply other threads:[~2015-11-02 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 15:57 [OSSTEST PATCH] build_clone: git clean newly cloned trees Ian Jackson
2015-10-29 16:01 ` Andrew Cooper
2015-11-02 14:19 ` Ian Campbell [this message]
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=1446473957.3088.48.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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 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.