linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org, Jon Loeliger <jdl@jdl.com>
Subject: Re: DTC 1.0.0 Release Coming?
Date: Mon, 6 Aug 2007 21:33:17 +0200	[thread overview]
Message-ID: <5fe57365c1fdd591c68546f4cb9347ba@kernel.crashing.org> (raw)
In-Reply-To: <20070801011900.GA31391@localhost.localdomain>

>>> Ok, figured out why.  When I push, then pop a quilt patch some of the
>>> files end up with their original contents, but changed timestamps.
>>> That altered stat information causes git-diff-index to give false
>>> indications of changed files, so setlocalversion adds the -dirty.
>>> Running git status, or gitool or various other things causes git to
>>> notice that the files aren't really changed, updates the index and
>>> then the version is generated correctly again.
>>>
>>> Not very robust though.
>>
>> Well you can't blame that on DTC's build system, nor on the
>> setlocalversion script, and not on Git either; it's a Quilt
>> problem...
>
> No, it's really not - touching the files on a pop is correct behaviour
> for quilt (that way it will correctly trigger a rebuild on make
> systems that aren't as flashy as Kbuild).

Yeah okay -- "it's a problem with how all these tools are used
together" :-)

> setlocalversion should be ensuring that the verison information is
> based on content, not stat info, which means it needs to do a git
> status or something that will remove the false positives before using
> git-diff-index to determine whether the tree is clean or not.

Yeah, that seems best.  Please fix this for the kernel version of
setlocalversion as well :-)


Segher

  reply	other threads:[~2007-08-06 19:33 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25 16:12 DTC 1.0.0 Release Coming? Jon Loeliger
2007-07-26  3:05 ` David Gibson
2007-07-26  7:25   ` David Gibson
2007-07-26 13:04   ` Jon Loeliger
2007-07-26 14:27     ` David Gibson
2007-07-26 15:21       ` Jon Loeliger
2007-07-27  1:33         ` David Gibson
2007-07-27  2:00           ` David Gibson
2007-07-31 21:11             ` Segher Boessenkool
2007-08-01  1:19               ` David Gibson
2007-08-06 19:33                 ` Segher Boessenkool [this message]
2007-08-06 13:48           ` Josh Boyer
2007-08-10  1:30             ` David Gibson
2007-08-10  1:37               ` Josh Boyer
2007-08-10  2:59                 ` David Gibson
2007-08-10 20:59                   ` Segher Boessenkool
2007-08-10 22:24                     ` Geoff Levand
2007-08-10 23:39                       ` Segher Boessenkool
2007-08-11  0:52                   ` Paul Mackerras
2007-08-11  1:35                     ` Geoff Levand
2007-08-12  9:26                       ` David Gibson
2007-08-13  1:39                         ` Stephen Rothwell
2007-08-12  9:25                     ` David Gibson
2007-08-10  2:13               ` Geoff Levand
2007-07-31 21:09 ` Segher Boessenkool
2007-08-01 23:35 ` Arnd Bergmann
2007-08-02  0:14   ` David Gibson

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=5fe57365c1fdd591c68546f4cb9347ba@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=jdl@jdl.com \
    --cc=linuxppc-dev@ozlabs.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).