Re: git-svn and repository hierarchy?
- From
- Peter Harris <git@peter.is-a-geek.org>
- Date
- Mar 6, 2009, 16:58 UTC
- Message-ID
- <eaa105840903060858g5b8f31bpb9a59d563835a9d5@mail.gmail.com>
- In-Reply-To
- <20090306161026.GA14554@raven.wolf.lan>
On Fri, Mar 6, 2009 at 11:10 AM, Josef Wolf wrote:
Show 7 quoted lines
> On Thu, Mar 05, 2009 at 02:48:14PM -0500, Peter Harris wrote: >> >> True, but in my experience it happens considerably less often with >> git. I find and fix most of my typos when reviewing my change-set >> before doing a "git push" or "git svn dcommit". > > So you are rewriting yourself but not accept rewrites by svn ;-)
No, I am not rewriting myself *after I publish*. I see the smiley, but I think you missed the point.
"git push" or "svn ci" is the end of the rewrites.
The critical difference is that I can easily manage an entire unpublished patch series in git. I cannot in svn (without 3rd party tools such as quilt or git-svn, anyway). So in svn if I notice a typo near the beginning of a patch series as I am publishing the last of the series, I'm screwed.
>> Indeed. Or even not-so-random names, such as cloneX/topic-name if you >> prefer. > > That would have the risk of multiple clones pushing to the same branch.
Only if cloneX pushes to cloneY/topic-name. Does each clone not have a unique name?
> Does that look sane?
No. But it doesn't look any more insane than any other workflow involving Subversion that I can think of. :-)
Peter Harris