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

Re: git newbie problems

From
GPGraham Percival <gpermus@gmail.com>
Date
Dec 6, 2006, 08:01 UTC
Message-ID
<457678BD.3050609@gmail.com>
In-Reply-To
<el5608$952$2@sea.gmane.org>
Jakub Narebski wrote:
Show 8 quoted lines
> Graham Percival wrote:
> 
>> flailed around looking for magic commands to make things work.  By "make 
>> things work", I mean imitating my work style with cvs:
> 
> Perhaps it would be better to at least read cvs-migration.txt
>   http://kernel.org/pub/software/scm/git/docs/cvs-migration.html
> and all tutorials.

I skimmed through the cvs-migration, the tutorial (part 1 and 2), and the "everyday git". I didn't notice any "how to deal with merges problems"... it was unfortunate that the merge problems arose the very first time I tried to upload my changes. If I had used git for a few days before it happened, I would have had more confidence to track down the problem (or email for help earlier!).

> There are some commands which CVS didn't have, and which are very useful
> with git: I'm talking here about "git show" (show latest change), "git
> log" (show kind of changelog), and gitk (graphical history viewer) or qgit
> (alternate graphical history viewer in Qt).

Yes, I don't doubt that git has many improvements -- the main developers of my project must have had some reason for moving away from cvs! I'm speaking as a new user who wants to get very simple work done. All I wanted to do was to fix a few typos in the lilypond documentation; the information about importing cvs projects or changing branches obscured the stuff I really wanted.

Show 5 quoted lines
> Yes, the git error messages certainly needs to be made more user-friendly.
> What git says here that one version has '.gitignore' file handled by version
> control, and second has it outside version control. At least I think what
> it does. "git ls-files --unmerged" or "git diff --merge --summary" should
> show 'true conflicts'.
Thanks for the suggestions!
> By the way, which version of git do you use? I think this particular check
> (if it is the case of this error) was relaxed.

git version 1.4.4.1 I installed it via fink/unstable on OSX.

Cheers,
Previous: Tom PrinceNext: Han-Wen Nienhuys
Message 10 of 38 in “git newbie problems”
  1. Graham PercivalDec 6, 2006
  2. Jakub NarebskiDec 6, 2006
  3. Han-Wen NienhuysDec 6, 2006
  4. Jakub NarebskiDec 6, 2006
  5. Han-Wen NienhuysDec 6, 2006
  6. Johannes SchindelinDec 6, 2006
  7. Junio C HamanoDec 6, 2006
  8. Daniel BarkalowDec 6, 2006
  9. Tom PrinceDec 6, 2006
  10. Graham PercivalDec 6, 2006
  11. Han-Wen NienhuysDec 6, 2006
  12. Junio C HamanoDec 6, 2006
  13. Jakub NarebskiDec 6, 2006
  14. Han-Wen NienhuysDec 6, 2006
  15. cvs-migration document: make the need for "push" more obviousJohannes Schindelin, Dec 6, 2006
  16. Jakub NarebskiDec 6, 2006
  17. Johannes SchindelinDec 6, 2006
  18. Jakub NarebskiDec 6, 2006
  19. New users, was Re: [PATCH] cvs-migration document: make the need for "push" more obviousJohannes Schindelin, Dec 6, 2006
  20. J. Bruce FieldsDec 6, 2006
  21. Han-Wen NienhuysDec 6, 2006
  22. J. Bruce FieldsDec 6, 2006
  23. Han-Wen NienhuysDec 6, 2006
  24. Johannes SchindelinDec 6, 2006
  25. J. Bruce FieldsDec 6, 2006
  26. J. Bruce FieldsDec 6, 2006
  27. Junio C HamanoDec 6, 2006
  28. Documentation: reorganize cvs-migration.txtJ. Bruce Fields, Dec 7, 2006
  29. Junio C HamanoDec 7, 2006
  30. J. Bruce FieldsDec 7, 2006
  31. Johannes SchindelinDec 7, 2006
  32. J. Bruce FieldsDec 7, 2006
  33. Johannes SchindelinDec 7, 2006
  34. J. Bruce FieldsDec 8, 2006
  35. Junio C HamanoDec 8, 2006
  36. J. Bruce FieldsDec 9, 2006
  37. Graham PercivalDec 6, 2006
  38. J. Bruce FieldsDec 6, 2006

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.