Re: [git-users] What's the best number of files within a single Git repository ?
On Thu, Jul 7, 2011 at 10:29 AM, CP cpcheng...@gmail.com wrote: We are evaluating migration our project to Git. It is said that we shouldn't put too many files in a single repo. or we will have performance issue. I've never heard of problems with the numbers of files. It is well known that very large files can be a problem but there are some workarounds (eg. git annex). Can you point to where the too many files issue has been discussed? -Brett. -- 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.
Re: [git-users] Any writers out there?
On Mon, Feb 7, 2011 at 3:31 PM, Mark (my words) elib...@gmail.com wrote: I'm new to git. I'm trying to develop a workflow for my creative writing. FWIW, I use git for just about every document I produce (report, paper, presentation). Most of the text is in LaTeX, notes using emacs's dot.org mode and sometime figures or pictures. I have one repo per project which is sometimes loosely defined. I don't use git submodules or similar but I do factor out some files to a common project (eg logos that get reused in many presentations). Even if I'm the only author it is useful to commit at points like first draft, draft for initial comments, comments from Fred addressed, final draft, final final draft and final final final dammit I mean it this time draft, etc. When I collaborate on a document I find it essential to put it in git (or other VC). Even if the other user doesn't use git (or other VC) it is helpful to track the contributions they feed you and avoid inadvertently stomping on text that they have modified. I agree with the others that auto-commits would give more problems than help as you wouldn't know which commit was meaningful. I guess you could label all auto commits with an empty message and then look for manual commits with a more meaningful comment (or with an explicit tag) but it's kind of a stretch. For your poems, if they tend to be short, I'd probably come up with some kind of collection rule and put each one in its own repo (eg. all cute bunny poems separate from all self-critical introspections). Oh, and one thing to be mindful of is text lines, particularly if you are using an unformatted source (like LaTeX, HTML, etc). Git wants to compare based on lines so make them as short and atomic as possible. Do try to use line breaks and not long monolithic lines as it makes comparing differences that much easier. This matters a lot when you need to merge two versions (eg two branches or incorporating stuff being fed by had from collaborators). -Brett. -- 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.
Re: [git-users] Paper on Git to Write, suggestions sought!
On Sun, Dec 5, 2010 at 7:12 PM, Neil Grogan n...@grogan.ie wrote: I have a paper to write in College on a SCM system and I choose Git. Just looking for one liners or links as to what you'd include or talk about? Specifically in the research or improvements in Git coming up, as I can't find much on that. I would include a discussion of Git's origin story. I find it interesting how Linus choose a proprietary VCS (BitKeeper) to manage what is arguably the single most successful free software project and how it inevitably blew up and out of the ashes rose Linus's second triumph. -Brett. -- 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-us...@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.
Re: [git-users] Command not found
On Thu, Nov 4, 2010 at 5:10 PM, Gareth gareth.b.fos...@gmail.com wrote: I've installed git using 'apt-get install git' - and ran fine. However - it doesnt seem to work. If I do a whereis git it returns nothing. Wow, in all my years of using Unix and Linux I've never heard of whereis! Try which git. FWIW, on my Ubuntu 10.10 system whereis git only returns the git.1 man page. -Brett. -- 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-us...@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 and tracking the branches of a partially forked project
Hi, Maybe this has nothing to do with the SVN part but I'd like some advice on how to stay in sync with multiple branches of an SVN project while maintaining my own local modifications in git. I'd like to apply my modifications starting at some early branch and then move them to each subsequent branch in an automated way, or at least one that minimizes conflicts. I've cloned the SVN repository with git-svn and have these remote branches: upstream/trunk upstream/branch/BRANCH1 upstream/branch/BRANCH2 upstream/tags/BRANCH1_TAG1 upstream/tags/BRANCH1_TAG2 upstream/tags/BRANCH2_TAG1 upstream/tags/BRANCH2_TAG2 what I want to end up with is a parallel set of local branches, like: local_trunk local_BRANCH1 local_BRANCH2 local_BRANCH1_TAG1 local_BRANCH1_TAG2 local_BRANCH2_TAG1 local_BRANCH2_TAG2 so that they have my local modifications to the corresponding remote branches. I think it can be assumed that BRANCH1_TAG1 and BRANCH1 share a common starting point on the SVN side. Thanks for any guidance, -Brett. -- 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-us...@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.
Re: [git-users] get rid of old commits
On Mon, Sep 20, 2010 at 11:57 AM, canna c.ne...@gmail.com wrote: the problem is, it's taking a lot of time for simple everyday operations Have you run git gc ever? -Brett. -- 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-us...@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 and --use-log-author --add-author-from = Unknown option.
Hi, I'm trying to sync one SVN repository to a sub directory of a second one using git-svn. I'll show how I'm mostly successfully doing that below. The problem I'm having is that I want the original commit author names to be preserved in the sync'ed repository. git-svn's man page talks about --use-log-author and --add-author-from which looks like just the ticket, however when I try to use the first to create the upstream connection I get: Unknown option: use-log-author And, similar when I add --add-author-from to create my downstream connection it complains that this flag is also unknown. I'm using 1.5.6.5 and have also tried 1.6.4.4. These flags were supposed to be added in 1.5.4. I tried sussing out the git git-svn code but didn't get very far and google failed me. Any ideas? -Brett. PS: for the record, and not that the details matter but here is how I am doing the sync w/out the problematic flags (watch for line wrap) # Initialize repository git-svn --id=upstream --svn-remote=upstream init --use-log-author --prefix=upstream/ --user=USER http://upstream.example.com/svn1/package git svn --id=downstream --svn-remote=downstream init --use-log-author --add-author-from --user=USER https://downstream.example.com/svn2/path/to/subdirectory/package git-svn fetch upstream git-svn fetch downstream git-checkout -t -b local-upstream upstream git-checkout -t -b local-downstream downstream # To do a sync: git checkout local-upstream git rebase local-downstream git checkout local-downstream git rebase local-upstream git-svn dcommit git branch -D local-upstream git checkout -t -b local-upstream upstream -- 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-us...@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 and --use-log-author --add-author-from = Unknown option.
On Tue, Dec 1, 2009 at 10:05 AM, Brett Viren brett.vi...@gmail.com wrote: Unknown option: use-log-author Digging into git-svn more I see the problem. This option is only defined for git-svn fetch or git-svn clone and not git-svn init. So it is a mismatch-bug between documentation and code. I'll submit a bug report. -Brett. -- 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-us...@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.
