Any interest in using git for scm?

[Darren Weber]

On Fri, Nov 6, 2009 at 9:05 PM, Darren Weber <dweber at macports.org> wrote:

>
> In any case, regardless of keyword problems (if they persist in git-svn),
> I'm glad to know that the svn repo is also in a git repo that is tracking
> the svn.  The git repo should provide more integrity than the svn repo and a
> reliable backup for the centralized svn repo.  (I have no idea, but I assume
> the Mac OS Forge guys have a backup system all wrapped up anyway, so not to
> worry about that.)  The point is that the algorithms in git for sha1 checks
> are not available in any other scm, AFAIK.
>
> One advantage of the sha1 hash is that it provides a truly unique ID for
> any commit, which probably surpasses the purpose of any $Id$ and other
> keywords for tracking commits.  Using global config settings, like
> user.name and user.email, the commits are automatically identified by the
> developer/commiter and they are useful in 'git blame'.  Looking at the git
> log --graph or using gitk and other git GUI tools gives a nice graph of the
> branch and commit history.  It seems easy to identify where any changes came
> from.  No need for an Id guidelines and associated developer conformity ;-)
> (That may be one reason that git doesn't support keywords ;-)).
>
> Take care,
> Darren
>
> PPS, For keyword issues, see:
>
> http://stackoverflow.com/questions/39742/does-git-have-anything-like-svn-propset-svnkeywords-or-pre-post-commit-hooks
>
> http://stackoverflow.com/questions/62264/dealing-with-svn-keyword-expansion-with-git-svn#72874
>
>
PS, Useful similarities between git and svn commands:
http://git.or.cz/course/svn.html





>
>
>
> On Fri, Nov 6, 2009 at 8:03 PM, Akira Kitada <akitada at macports.org> wrote:
>
>> Hello Darren,
>>
>> I posted a similar question on the list before and failed :-)
>>
>> http://marc.info/?t=124395706900073&r=1&w=2
>>
>> On Fri, Nov 6, 2009 at 10:46 AM, Darren Weber <dweber at macports.org>
>> wrote:
>> >
>> > After listening to Linus Torvalds talk about git and looking at a video
>> > tutorial from Scott Chacon, it would seem beneficial to use git for
>> MacPorts
>> > development.  It appears that git can be used with an existing svn
>> > repository (man git-svn), or the svn repository could be imported into a
>> new
>> > master git repository (perhaps host it with github).  Is anyone
>> currently
>> > using git for MacPorts development?
>> >
>> > After a few tips from MacPorts gurus and some experiments, I was able to
>> > draft the instructions at
>> >
>> > Create an experimental users directory in the MacPorts Subversion
>> repository
>> >
>> > http://trac.macports.org/wiki/CommittersTipsAndTricks
>> >
>> > The merge process with svn takes a while to grok, but it works OK.  Is
>> > anyone having an easier time with git?
>> >
>> > The resources here are helpful in learning git:
>> > http://www.linuxfoundation.org/search/node/git
>> >
>> > Take care,
>> > Darren
>> >
>> >
>> > _______________________________________________
>> > macports-dev mailing list
>> > macports-dev at lists.macosforge.org
>> > http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
>> >
>> >
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20091106/99b34d81/attachment-0001.html>