Re: Bug 455400

On 7/31/07, Mark Dexter <dextercowley gmail com> wrote:

Also, I still would like answers to my questions about how to find and
download uncommitted documentation patches (so I can start with the latest

Hi, I have been following this thread and from what I understand,
there are two people working on documentation. You are trying to keep
sync with each other's patches because they have not been merged into
the dia SVN repository yet. All this would have been easy if dia was
in a distributed system like git or darcs, where people can directly
send patches to each other without waiting to commit to the main

git-svn actually allows you to maintain your own stuff in git, and
still work with the main SVN repository. Would you consider using
git-svn? I am aware the learning curve involved is pretty steep, and
your focus is on getting documentation done, and not wade through
software manuals. But do take a look and if you think its worth the
trouble, you could try it out.

I myself have little experience with git, so this is basically just a
shot in the dark. I won't be able to offer any help if you want to try
it. I do intend to use it myself when I get the time to learn the
ropes. The intention is to keep my own patches separate from each
other until they are committed to the SVN repository.

A tutorial introduction to git

git-svn Manual Page

And here's what I mean by a steep learning curve. From the git-svn manpage:
git-svn is a simple conduit for changesets between Subversion and git.
git-svn was originally designed for an individual developer who wants
a bidirectional flow of changesets between a single branch in
Subversion and an arbitrary number of branches in git.

If those two sentences make sense to you, you are half-way there already. :)

Research Scholar, Department of CSE, IIT Bombay

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]