On Sun, 14 Nov 2010 05:51:43 -0200 Gustavo Sverzut Barbieri
<barbi...@profusion.mobi> said:

> On Sun, Nov 14, 2010 at 5:24 AM, Jesse Charbneau <j...@thecharbneaus.com>
> wrote:
> > Hello,
> >   I have modified the contribute and support pages.  Please review and let
> > me know if I’m heading in the right direction or not.  Basically shifted
> > things to a single frame layout, removed some items others had proposed as
> > wiki bound and reworded some text here and there.  Also let me know if the
> > knife went too deep and I can add items/sections back in as needed/directed.
> >  I could use some direction on if I should also work some of the items in
> > the wiki and migrate the content there, etc.  If I should do that, please
> > direct me on how to create a wiki account (sorry, I’ve looked but haven’t
> > found a “user registration” page - could be I’m blind so please confirm if
> > true :-) ).
> 
> text seems fine. I'd add a <strong> over the "If you're not a
> developer" in the contribute page. So people can jump straight there
> if not a dev ;-)
> 
> Also, remove that git-svn madness raster said. It's bullshit, if git
> users like git-svn, they will already know about that. Likely we can
> add to wiki's ECoding or Guidelines that if you plan to create a patch
> set, as opposed to a single patch, one can use either git or quilt
> (http://linux.die.net/man/1/quilt). Actually, for this case doing a
> full git-svn clone is stupid, the easiest way to work is:
> 
> svn clone
> git init; git add .; git commit -m "initial svn clone at `svnversion`"
> make maintainer-clean
> svn up
> git add ...; git commit -m "svn up to `svnrevision`"
> $EDITOR file.c
> git commit file.c -m "my changes"
> $EDITOR file2.c file3.c
> git commit file2.c file3.c -m "fix problems in xyz"
> $EDITOR file1.c
> git commit file1.c -m "fix previous commit 'my changes'"
> ...
> svn up
> git add ...; git commit -m "svn up to `svnrevision`"
> ...
> # okay, ready to send patches: rebase to reorder and merge/squash patches:
> git rebase -i
> # move all "svn up" before your patches:
> p a1b2c3 svn up 1234
> p f1s4c2 svn up 1245
> p abacad "my changes"
> f cdyded "fix previous commit 'my changes'"
> p 112233 "fix problems in xyz"
> 
> git format-patches -2 # create patches for last two patches

but thats what git svn ends up doing for you... and the reason i put it there
is that there are actual git repos that have totally lost all links to the svn
original and are getting hand-patched 1 commit at a time - people using git
didn't use or know about git-svn or use svn and git together in the same tree
and created a forked tree as a result of this. giving this information is good
as hopefully it prevents future such problems. i wrote that there for a good
reason - i've seen what happpens.

> -- 
> Gustavo Sverzut Barbieri
> http://profusion.mobi embedded systems
> --------------------------------------
> MSN: barbi...@gmail.com
> Skype: gsbarbieri
> Mobile: +55 (19) 9225-2202
> 
> ------------------------------------------------------------------------------
> Centralized Desktop Delivery: Dell and VMware Reference Architecture
> Simplifying enterprise desktop deployment and management using
> Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
> client virtualization framework. Read more!
> http://p.sf.net/sfu/dell-eql-dev2dev
> _______________________________________________
> enlightenment-devel mailing list
> enlightenment-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    ras...@rasterman.com


------------------------------------------------------------------------------
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
client virtualization framework. Read more!
http://p.sf.net/sfu/dell-eql-dev2dev
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to