git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Ignore version update changes on git show report?

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Mar 1, 2013, 13:33 UTC
Message-ID
<5130AE23.4040303@drmicha.warpmail.net>
In-Reply-To
<DEC76CB0-9E35-40A8-9D73-77617CC605A3@gmail.com>
Preben Liland Madsen venit, vidit, dixit 26.02.2013 20:53:
Show 20 quoted lines
> Hello, 
> 
> I'm trying to investigate some what changes have been done between two versions of a software with the name IP.Board. 
> 
> This proves more troublesome than I thought, since their release builder appearantly updates the version number automatically in all files. 
> 
> This causes a lot of files to have this as the only change: 
> 
> - * IP.Board v3.4.2
> + * IP.Board v3.4.3
> 
> Which is quite annoying to have to go through and therefor is responsible for more than 800 files being changed. 
> 
> Is there some sort of git command or command I can combine together with git show that will ignore files with only these changes? Something along the lines of ignoring files where the only change matches this change or ignore files that've only gotten 1 line removed and 1 line added? 
> 
> Best regards, Preben--
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
First of all, there is
git beat-with-stick
that you should apply to those responsible for that mess ;)

If you have to deal with that sort of situation then a textconv filter might get you as close as possible. Use "grep -v '^\* IP.Board v*'" as a textconv filter for those files, and those changes will disappear from the diff. (I do something like that for tracking my gitk config, which stores last window sizes.)

Michael
Previous: Preben Liland MadsenNext: Preben Liland Madsen
Message 2 of 3 in “Ignore version update changes on git show report?”
  1. Preben Liland MadsenFeb 26, 2013
  2. Michael J GruberMar 1, 2013
  3. Preben Liland MadsenMar 1, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.