JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for STARDEV Archives


STARDEV Archives

STARDEV Archives


STARDEV@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

STARDEV Home

STARDEV Home

STARDEV  May 2010

STARDEV May 2010

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: submodules... uncommitted changes?

From:

"Peter W. Draper" <[log in to unmask]>

Reply-To:

Starlink development <[log in to unmask]>

Date:

Tue, 25 May 2010 23:05:14 +0100

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (101 lines)

On Tue, 25 May 2010, Edward Chapin wrote:

> Date: Tue, 25 May 2010 14:30:51 -0700

> I suspect this is something that's already been discussed before, but I
> don't get what's happening.

Hi Ed,

this all seems a bit wacky. Normally if you see the below I'd just do:

   ./update-modules

and if that refused and I knew I had no local modifications in the
submodule that I wanted to keep, I'd do:

   ./update-modules -f

Usually you would only see these submodules as modified if they were out
of date, but sometimes you can get locally modified files, usually
generated ones, which the second case will fix. Maybe you have something
setup that is causing modified files to be generated when normally this
wouldn't happen. This could be caused by inconsistent file timestamps.

If you see this again send the full output from ./update-modules which
should show what has been modified.

One final thought if you have a long lived branch then you will need to
rebase that against master and run update-modules to get back into sync
with changes to the expected submodule SHA. If you don't do that you'll
constantly find the submodules look out of sync.

cheers,

Peter.

> On one of my machines a bunch of submodules keep claiming to have
> uncommitted changes, e.g.
>
> $ git status
> # On branch master
> # Changed but not updated:
> #   (use "git add <file>..." to update what will be committed)
> #   (use "git checkout -- <file>..." to discard changes in working directory)
> #
> #	modified:   thirdparty/apache/xerces-c/xerces-c
> #	modified:   thirdparty/heasarc/cfitsio/cfitsio
> #	modified:   thirdparty/latex2html/latex2html/latex2html
> #	modified:   thirdparty/rit/match/match
> #	modified:   thirdparty/tclsys/blt/blt
> #	modified:   thirdparty/tclsys/itcl/iwidgets
> #	modified:   thirdparty/tclsys/tclx/tclx
> #	modified:   thirdparty/tclsys/tkimg/tkimg
> #
>
> If I look at this in gitk I notice "dirty" appended to the commit SHA1 in
> the lower-left box, i.e.
>
> --------------------- thirdparty/apache/xerces-c/xerces-c ---------------------
> Submodule thirdparty/apache/xerces-c/xerces-c 65e349f..65e349f-dirty:
>
> ---------------------- thirdparty/heasarc/cfitsio/cfitsio ----------------------
> Submodule thirdparty/heasarc/cfitsio/cfitsio 744c584..744c584-dirty:
>
> ----------------- thirdparty/latex2html/latex2html/latex2html -----------------
> Submodule thirdparty/latex2html/latex2html/latex2html eee1edc..eee1edc-dirty:
>
> -------------------------- thirdparty/rit/match/match --------------------------
> Submodule thirdparty/rit/match/match 4e60352..4e60352-dirty:
>
> -------------------------- thirdparty/tclsys/blt/blt --------------------------
> Submodule thirdparty/tclsys/blt/blt 3628f25..3628f25-dirty:
>
> ----------------------- thirdparty/tclsys/itcl/iwidgets -----------------------
> Submodule thirdparty/tclsys/itcl/iwidgets 291b8e2..291b8e2-dirty:
>
> ------------------------- thirdparty/tclsys/tclx/tclx -------------------------
> Submodule thirdparty/tclsys/tclx/tclx 9ff2b9b..9ff2b9b-dirty:
>
> ------------------------ thirdparty/tclsys/tkimg/tkimg ------------------------
> Submodule thirdparty/tclsys/tkimg/tkimg b021c86..b021c86-dirty:
>
>
> I've tried things like git clean -fdx on these directories, I've run
> update-modules, clean-modules, and remove-modules. Finally I even deleted
> the whole thirdparty tree and did a fresh git checkout thirdparty,
> ./update-modules, re-bootstrapped, configured, removed from manifests and
> then make-world. I still end up with these same "dirty" messages.
>
> I believe when I first did the checkout and update-modules I don't see the
> "dirty" message.
>
> What's going on here / how do I make these messages go away?
>
> thanks,
> Ed
>

-- 
Peter W. Draper, http://astro.dur.ac.uk/~pdraper

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

December 2023
January 2023
December 2022
July 2022
June 2022
April 2022
March 2022
December 2021
October 2021
July 2021
April 2021
January 2021
October 2020
September 2020
August 2020
May 2020
November 2019
October 2019
July 2019
June 2019
February 2019
January 2019
December 2018
November 2018
August 2018
July 2018
May 2018
April 2018
March 2018
February 2018
December 2017
October 2017
August 2017
July 2017
May 2017
April 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
October 2015
September 2015
August 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
2004
April 2003
2003


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager