hi, On Wed, Jan 8, 2014 at 10:20 AM, <k...@aspodata.se> wrote:
> Joram: > > Simon Bailey: > > > so, my follow up question: why use git as a single user? > > > > I always use git, event git-svn for svn repos. > > Comparing to CVS and SVN, I see these advantages: > > > > - easy branching > what for when working with scores? > > - I am a heavy user of git rebase > which does what? > > - being able to commit, branch, diff etc. without internet connection > how often do you branch or diff when working on scores? > > that way I can work on a train, for example > hmm. i do a lot of work on trains. however, i have a data plan on my phone which i use for tethering if i need a connection. > > - this makes the commit often & early paradigm easy > i understand this when working on software programs. but on music scores? With svn/cvs you need more-or-less a permanent connection to > "the server". With git I can work off-line and update (both ways) > when connected. > i only need the connection with SVN if i'm actually committing. with git i can commit offline, but then when i get a data connection i have to commit again to the repo? that's two steps compared to one with SVN. i still don't get it. especially as i generally commit when i reach certain milestones or at the end of a working day. don't get me wrong, i'm really trying to find a reason to like git. but nothing seems different to SVN so far, except for the fact that i have to commit TWICE... Urs also pointed out: On Tue, Jan 7, 2014 at 2:51 PM, Urs Liska <u...@openlilylib.org> wrote: > Ah, finally one idea about your question, not based on experience but on > randomly read statements: How can you use branches with SVN? If it's > correct that Git branches are conceptually different through being so > exceptionally light-weight then I'd think this _is_ an advantage even for a > single user. $ svn copy <repo>/trunk <repo>/branch/my-branch from http://svnbook.red-bean.com/en/1.8/svn.branchmerge.using.html : <<< Subversion's repository has a special design. When you copy a directory, you don't need to worry about the repository growing huge—Subversion doesn't actually duplicate any data. Instead, it creates a new directory entry that points to an existing tree. If you're an experienced Unix user, you'll recognize this as the same concept behind a hard link. As further changes are made to files and directories beneath the copied directory, Subversion continues to employ this hard link concept where it can. It duplicates data only when it is necessary to disambiguate different versions of objects. >>> sounds fairly lightweight to me too... ;) (this is also the same workflow for tags). regards, sb -- Do not meddle in the affairs of trombonists, for they are subtle and quick to anger.
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
