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

Re: Git drawbacks?

From
Dmitry Potapov <dpotapov@gmail.com>
Date
Nov 10, 2009, 13:45 UTC
Message-ID
<20091110134540.GK27126@dpotapov.dyndns.org>
In-Reply-To
<loom.20091110T092404-595@post.gmane.org>
On Tue, Nov 10, 2009 at 08:31:48AM +0000, Dmitry Smirnov wrote:
Show 17 quoted lines
> Dmitry Potapov <dpotapov <at> gmail.com> writes:
>  
> > Yes, but then I do not see any reason to do any time consuming building
> > and testing in the working tree. I create a snapshot of the interesting
> > version using 'git archive' and then run build&test on it... In this
> > way, I can make sure that the archive I deliver is tested properly. If
> > you do your testing in the working tree, sometimes uncommitted or some
> > other files that are left over from previous builds may affect result.
> > So, if it takes considerable time anyhow, why do not do clean build and
> > test? And if you worry about compilation time, you can use ccache.
> 
> It is not clear for me. Yes, I have to get some fixed version to reproduce
> the bug reported by someone. Then I need to fix it and commit the change 
> back (on the head). Also, it is obvious to reproduce the issue and 
> test the fix on the tip. Can do this with 'git archive'?
> BTW, doesn't 'git archive' sync to some version that I probably already 
> have in other clone? ;-)

I am not sure I understood your question. What 'git archive' does is to create a tar or zip archive or any version that you specify. So, you can use it to export the snapshot of any version to a temporary directory for testing if this testing takes a noticeable time and you want to be able to work on something else in meanwhile. If necessary, you can create a temporary branch starting at the intesting point and to add some commits there (such as a new test case to reproduce the problem) and then run test on it. Later, you can either rebase or merge these commits to any branch that needs them.

Actually, when someone reports a problem, I do not use 'git archive' because I write a test case for this bug and run it alone, and it does not take much time to run it. But periodically (a few times a day), I run the full test suit, which takes considerable amount of time, so I run this test outside of my working directory, using 'git archive'.

Dmitry
Previous: Dmitry SmirnovNext: Dmitry Smirnov
Message 15 of 27 in “Git drawbacks?”
  1. Dmitry SmirnovNov 6, 2009
  2. Avery PennarunNov 6, 2009
  3. Dmitry SmirnovNov 6, 2009
  4. Jacob HelwigNov 6, 2009
  5. Avery PennarunNov 6, 2009
  6. david@lang.hmNov 6, 2009
  7. Dmitry SmirnovNov 9, 2009
  8. Jacob HelwigNov 9, 2009
  9. Dmitry SmirnovNov 9, 2009
  10. Jacob HelwigNov 9, 2009
  11. Dmitry PotapovNov 9, 2009
  12. Dmitry SmirnovNov 9, 2009
  13. Dmitry PotapovNov 9, 2009
  14. Dmitry SmirnovNov 10, 2009
  15. Dmitry PotapovNov 10, 2009
  16. Dmitry SmirnovNov 10, 2009
  17. Paolo BonziniNov 10, 2009
  18. B Smith-MannschottNov 9, 2009
  19. Dmitry PotapovNov 9, 2009
  20. Dmitry SmirnovNov 10, 2009
  21. Dmitry PotapovNov 10, 2009
  22. Dmitry SmirnovNov 10, 2009
  23. Paolo BonziniNov 10, 2009
  24. Dmitry PotapovNov 10, 2009
  25. Dmitry SmirnovNov 10, 2009
  26. Dmitry SmirnovNov 9, 2009
  27. Dmitry SmirnovNov 11, 2009

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.