[ELDK] Problems rebuilding ELDK-4.1 from scratch (RCS keyword expansion)

[J.T. Conklin]

On Wed, Mar 18, 2009 at 6:10 AM, Wolfgang Denk <wd at denx.de> wrote:
>> I have run into a problem with the ELDK patch files not matching the
>> code from the SRPMs due to RCS $Id: $ keywords being different.  All
>> the patch files appear to have keyword expansion disabled, so RCS Id's
>> are $Id$.
>
> Hm... this is very strange. This sounds as if you were using CVS in
> any step of your way (without setting the -ko option correctly).

Had I been using CVS in any way, I would agree.

>> Is this a problem with the files in the repo, or in how I checked the
>> files with git?
>
> It sounds to me like an error when cloning the git repository - which
> exact command did you use? Did you follow the instructions in the
> Application Note at
> http://www.denx.de/wiki/DULG/AN2009_02_EldkReleaseBuildEnvironment ?

I checked out the files with git-clone like:

$ git-clone git://www.denx.de/git/eldk/build
Initialized empty Git repository in /home/jtc/eldk-git/build/.git/
remote: Counting objects: 9058, done.
remote: Compressing objects: 100% (3786/3786), done.
remote: Total 9058 (delta 4003), reused 7685 (delta 3175)
Receiving objects: 100% (9058/9058), 4.31 MiB | 319 KiB/s, done.
Resolving deltas: 100% (4003/4003), done.
Checking out files: 100% (585/585), done.

And then changed it to the 4.1 branch with git-checkout:

$ cd build; git-checkout ELDK_4_1
Note: moving to "ELDK_4_1" which isn't a local branch
If you want to create a new branch from this checkout, you may do so
(now or later) by using -b with the checkout command again. Example:
  git checkout -b <new_branch_name>
HEAD is now at 37607a7... Update README files as last step for release.

I just did it again, and all the $Id: ... $'s had been expanded as $Id$.

Many thanks,

    --jtc