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

Re: Memory overrun in http-push.c

From
EREygene Ryabinkin <rea-git@codelabs.ru>
Date
Mar 1, 2007, 12:00 UTC
Message-ID
<20070301120042.GD63606@codelabs.ru>
In-Reply-To
<200703011040.35971.andyparkins@gmail.com>
Good day!
> was more annoyed by the fact that the patch was an attachment,
> than it was generated by diff without leading a/ and b/ paths.

So, git is unable to use this type of patches directly and I will need to do $ patch < patchfile $ rm file.orig $ git commit

Just wondering what is bad with the diffs without leading a/ and b/.
> I certainly wasn't suggesting that it should be a requirement.  I just thought
> there was a certain irony.  Perhaps even a lesson to be learned - find out 
> why someone has chosen (even with git in front of them and deep enough inside 
> to find bugs in it), not to use git.

I've just realized that I need git because I need disconnected commits. That's why I left my beloved SVN and started to hack GIT ;))

By the way, I am missing one thing: the Id keyword in the file. The problem is that when some user is telling me: there is a bug in the function a() that is inside the file b.c, then I can ask him to give me the $Id$ tag of the file and I will have the full information about the file version. Can I have it with git if user has just the sources without any signs of the file versions? I've glanced over the git manual, but was unable to find anything usable.

Show 17 quoted lines
> I think there is a usability lesson to be pulled from this situation.  Why 
> didn't Eygene just say:
> 
>  $ tar zxvf git-tarball.tgz
>  $ cd git
>  $ git init
>  $ vim http-push.c
>  $ git diff
> 
> Note, that was not an attack on Eygene - I genuinely am interested to know 
> where we should put the documentation that tells a new user what they need to 
> know quickly.
> 
> Somehow, git has failed this person.  I was simply wondering in what way.
> 
> However, Eygene's response made it sound like a situational thing - it was 
> inconvenient to actually install git.  Fair enough.

Not incovinient to install git, but it was just convinient to me to use FreeBSD port. The other way round ;))

-- 
Eygene
Previous: Andy ParkinsNext: Junio C Hamano
Message 12 of 39 in “Memory overrun in http-push.c”
  1. Eygene RyabinkinFeb 28, 2007
  2. Andy ParkinsFeb 28, 2007
  3. Johannes SchindelinFeb 28, 2007
  4. Eygene RyabinkinMar 1, 2007
  5. Alex RiesenMar 1, 2007
  6. Eygene RyabinkinMar 1, 2007
  7. Alex RiesenMar 1, 2007
  8. Eygene RyabinkinMar 1, 2007
  9. Junio C HamanoMar 1, 2007
  10. Alex RiesenMar 1, 2007
  11. Andy ParkinsMar 1, 2007
  12. Eygene RyabinkinMar 1, 2007
  13. Junio C HamanoMar 1, 2007
  14. Eygene RyabinkinMar 1, 2007
  15. Johannes SchindelinMar 1, 2007
  16. Andy ParkinsMar 1, 2007
  17. Johannes SchindelinMar 1, 2007
  18. Andy ParkinsMar 1, 2007
  19. Johannes SchindelinMar 1, 2007
  20. Andy ParkinsMar 2, 2007
  21. Jakub NarebskiMar 2, 2007
  22. Andy ParkinsMar 2, 2007
  23. Johannes SchindelinMar 2, 2007
  24. Andy ParkinsMar 2, 2007
  25. Daniel BarkalowMar 4, 2007
  26. Junio C HamanoMar 4, 2007
  27. Daniel BarkalowMar 4, 2007
  28. Alex RiesenMar 1, 2007
  29. Shawn O. PearceMar 1, 2007
  30. Uwe Kleine-KönigMar 1, 2007
  31. Jakub NarebskiMar 2, 2007
  32. Johannes SchindelinMar 2, 2007
  33. identifying blobs (was Re: Memory overrun in http-push.c)Junio C Hamano, Mar 2, 2007
  34. Linus TorvaldsMar 2, 2007
  35. Andy ParkinsMar 2, 2007
  36. Matthieu MoyMar 2, 2007
  37. Andy ParkinsMar 2, 2007
  38. Florian WeimerFeb 28, 2007
  39. Eygene RyabinkinMar 1, 2007

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.