[git-users] Re: Questions about git - don't read if you not want to answer newbie questions
On 22/10/09 m.m-o.net said: > I ll have to cooperate in a group with 3 other students and wanted to > ask how to do so with git. Everyone working on his part of the project Work any way you like. That's kinda the point. :) How would you like to work? Mike -- Michael P. Soulier "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein pgpw8uNe2R1X8.pgp Description: PGP signature
[git-users] Questions about git - don't read if you not want to answer newbie questions
Hi, I ll have to do a lot of group work and programming stuff during this semester so I thought I could give git a go as my future versioning system. I ll have to cooperate in a group with 3 other students and wanted to ask how to do so with git. Everyone working on his part of the project but how to put our works together? though Git is distributed - is there a easy way to use a common repo where everyone puts selective changes to? Or if I am totally wrong tell me how we can handle our situation the best way? regards m.m-o.net --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Git for human beings" group. To post to this group, send email to git-users@googlegroups.com To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/git-users?hl=en -~--~~~~--~~--~--~---
[git-users] Re: git-svn equivalent for "hg incoming"?
On 20/10/09 Douglas Alan said: >% hg incoming > > if you want to see what the pull will do before you actually do it. I > was imagining that adding the "-n" option to "git svn rebase" would be > the equivalent. > > I.e., like so: > >% git svn rebase -n > > But the above really doesn't reveal much information at all. > > So, what, dear friends, is the proper git-svn equivalent for "hg > incoming"? I don't use git-svn much, but the plain git equivalent would be git fetch # update local object store git log master..origin/master # show me what's in the master branch on # origin that I don't have locally Mike -- Michael P. Soulier "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein pgp8R15Bto4h4.pgp Description: PGP signature
[git-users] Re: Comment commits using accents
On Oct 20, 3:50 pm, Paulo Cassiano wrote: > I tryed to set the i18n as you ask me to do, but doesn't work... My > DOS prompt shows me characters like ... in the accents > place... > > Now I'll try to set a default editor. I hope this works for me. [...] Oh, and there can also be a problem with `less`, if it's used as a pager in the console. I use an old like dirt hack to make it have no problems with Cyrillic characters -- creating the LESSCHARSET environment variable set to "koi8-r". This won't work for you, so probably try to employ another hack with setting pager=less -FRX as Michael P. Soulier suggested earlier in this thread -- it might fix your problem. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Git for human beings" group. To post to this group, send email to git-users@googlegroups.com To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/git-users?hl=en -~--~~~~--~~--~--~---
[git-users] Re: Comment commits using accents
On Oct 20, 3:50 pm, Paulo Cassiano wrote: > I tryed to set the i18n as you ask me to do, but doesn't work... My > DOS prompt shows me characters like ... in the accents > place... > > Now I'll try to set a default editor. I hope this works for me. [...] If you managed to make several commits with i18n.commitencoding *not* set to the charset matching your windows' code page, then commit messages of those commits are messed because Git interprets them as UTF-8. i18n.commitencoding setting makes Git add special header to every commit object you're making, so that it's able to re-encode commit messages to your local charset when you do `git log` or equivalent. So that option only affects commits made after it was set. If it's not the case, re-check whether the option is really set and spelled correctly by running git config --list | findstr commitencoding in your repository's working directory. The best bet is just to create a test repository from scratch, set the option being discussed on it, make several commits with non-ASCII messages and verify everything works OK, including the output of `git log` and the display in gitk. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Git for human beings" group. To post to this group, send email to git-users@googlegroups.com To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/git-users?hl=en -~--~~~~--~~--~--~---
[git-users] Re: Comment commits using accents
I tryed to set the i18n as you ask me to do, but doesn't work... My DOS prompt shows me characters like ... in the accents place... Now I'll try to set a default editor. I hope this works for me. Thanks! On Oct 19, 12:49 pm, Konstantin Khomoutov wrote: > On Oct 19, 3:44 pm, Paulo Cassiano wrote: > > > I'm using Git temporarily in a Windows Vista machine and trying to > > comment my commits in portuguese, using accents, but my console > > doesn't show my comments properly... > > > I've tried to change my console encoding from default to UTF-8 or to > > 1251(2), but the problem persist... > > > How could I fix this? > > For unknown reason Git was not made to work with user's locale > codeset, > and it assumes you feed it with UTF-8 on any platform. > To make it use ISO-8859-1, which is used for Portuguese, as I > understand, > you have to manually set the "commit encoding" for your repository, > like this: > > git config i18n.commitencoding iso-8859-1 > > This will match the Windows-1252 encoding which is supposedly the code > page for your locale. Setting i18n.commitencoding to "windows-1252" > should also work by the way. > > Note that if you're sharing this repository with anyone else, they're > all supposed to perform the same configuration step on their local > copy of the repository, as now all commit messages will be encoded in > iso-8859-1. > > Refer to git-show man page for more details (run `git help show`). --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Git for human beings" group. To post to this group, send email to git-users@googlegroups.com To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/git-users?hl=en -~--~~~~--~~--~--~---
[git-users] git-svn equivalent for "hg incoming"?
Hi. I'm much more familiar with Mercurial than I am with Git, but I've decided to take the plunge into Git so that I can use git-svn. Now, I know that % git svn rebase is kind of like % hg pull With Mercurial, however, you can do % hg incoming if you want to see what the pull will do before you actually do it. I was imagining that adding the "-n" option to "git svn rebase" would be the equivalent. I.e., like so: % git svn rebase -n But the above really doesn't reveal much information at all. So, what, dear friends, is the proper git-svn equivalent for "hg incoming"? Thanks, |>ouglas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Git for human beings" group. To post to this group, send email to git-users@googlegroups.com To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/git-users?hl=en -~--~~~~--~~--~--~---
