Fwd: Git users: bring out your bugbears!
Hi Everyone One of my colleagues from work is off to a git get together, and Is asking if anyone has anything they really wish was different with git. I said I would ask the koha developers as we have used git for a while now. So any suggestions send them my way and I will pass them on to Sam. Chris ---------- Forwarded message ---------- Hi all, For some strange reason the Git project is again flying me over to Silly Valley for the Google Summer of Code Mentor Summit. And right after that I've got a thrilling 3 days of GitTogether™. This is a meeting with many core git developers to discuss direction for git - see http://git.or.cz/gitwiki/GitTogether09 What I'd appreciate is for people to drop me some notes about what you've found annoying in git or room for improvement - especially from those people who have had to teach it to new members in their team the most. One of the things I want to focus on are submodules - I hear from a lot of people that they suck and would like to hear from you why. If you have time to write, please do - otherwise if you'd prefer a face to face rant showing with example that's all good too. If there is sufficient interest in this I could schedule a brief workshop on it. I'm flying out in a week, so it needs to be between now and then. Cheers! Sam ----- End forwarded message -----
Chris Cormack wrote:
One of my colleagues from work is off to a git get together, and Is asking if anyone has anything they really wish was different with git. I said I would ask the koha developers as we have used git for a while now. So any suggestions send them my way and I will pass them on to Sam
Yes! Please flatten the learning curve or at least make it less steep. Yes again! Provide some git for idyots doco. And again! Provide some hybrid (macro?) commands that make it conceptually easier for those coming from CVS to use git. thanks rick (ducking for cover) -- _________________________________ Rick Welykochy || Praxis Services "A Ministry of Defence guide to preventing information leaking into the public domain has leaked into the public domain."
Rick Welykochy wrote:
Chris Cormack wrote:
One of my colleagues from work is off to a git get together, and Is asking if anyone has anything they really wish was different with git. I said I would ask the koha developers as we have used git for a while now. So any suggestions send them my way and I will pass them on to Sam
Some of the errors and recovery procedures are a bit confusing. The one which got me yesterday is the error "File exists" when another user with a too-secure umask has created files in the git repository. What it actually meant was that the file exists and my git couldn't delete/modify it.
Yes! Please flatten the learning curve or at least make it less steep.
How?
Yes again! Provide some git for idyots doco.
What exactly do you want? There's already http://www.kernel.org/pub/software/scm/git/docs/everyday.html in the distribution and others outside it like http://wiki.sourcemage.org/Git_Guide
And again! Provide some hybrid (macro?) commands that make it conceptually easier for those coming from CVS to use git.
One problem is that CVS is actually conceptually broken, which was part of the motive for git, but there's http://git.or.cz/course/cvs.html (which uses cg not git, but I think the actual commands in light blue are interchangable apart from the switch command); or http://www.chem.helsinki.fi/~jonas/git_guides/HTML/CVS2git/CVS2git.html#SECT... Hope that helps, -- MJ Ray (slef) LMS developer and webmaster at | software www.software.coop http://mjr.towers.org.uk | .... co IMO only: see http://mjr.towers.org.uk/email.html | .... op
A feature allowing the easy preservation of commit history in Git which follows the new location of files when they are moved for reorganisation would be great. Understanding the code and preserving correct attribution would be much improved by such a feature. Most every programming tool could use more informative error messages. Thomas Dukleth Agogme 109 E 9th Street, 3D New York, NY 10003 USA http://www.agogme.com +1 212-674-3783 On Thu, October 15, 2009 04:10, Chris Cormack wrote:
Hi Everyone
One of my colleagues from work is off to a git get together, and Is asking if anyone has anything they really wish was different with git. I said I would ask the koha developers as we have used git for a while now. So any suggestions send them my way and I will pass them on to Sam.
Chris
---------- Forwarded message ----------
Hi all,
For some strange reason the Git project is again flying me over to Silly Valley for the Google Summer of Code Mentor Summit. And right after that I've got a thrilling 3 days of GitTogether™. This is a meeting with many core git developers to discuss direction for git - see http://git.or.cz/gitwiki/GitTogether09
What I'd appreciate is for people to drop me some notes about what you've found annoying in git or room for improvement - especially from those people who have had to teach it to new members in their team the most.
One of the things I want to focus on are submodules - I hear from a lot of people that they suck and would like to hear from you why.
If you have time to write, please do - otherwise if you'd prefer a face to face rant showing with example that's all good too. If there is sufficient interest in this I could schedule a brief workshop on it.
I'm flying out in a week, so it needs to be between now and then.
Cheers! Sam
----- End forwarded message ----- _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
On 2009/10/16, at 4:13 PM, Thomas Dukleth wrote:
A feature allowing the easy preservation of commit history in Git which follows the new location of files when they are moved for reorganisation would be great.
Understanding the code and preserving correct attribution would be much improved by such a feature.
hmm, that *is* a good suggestion i thought that either 'git-mv' or git-rename' did this, but a quick google-about says they dont - i'm surprised...
Most every programming tool could use more informative error messages.
yep, thats a given, so get writing those man-pages and wiki-docs everyone! ;)
participants (5)
-
Chris Cormack -
Mason James -
MJ Ray -
Rick Welykochy -
Thomas Dukleth