Re: Public Git repo: Status update

2011-01-11 Thread John Ralls
On Jan 11, 2011, at 8:23 PM, Yawar Amin wrote: > Hi John, > > Trying to understand your suggestion. Questions below: > > On 2011-01-08, at 17:16, John Ralls wrote: > >> […] >> >> Maybe instead you could create a fake-master branch off of master in your >> git-svn repo and tie fake-master to

Re: Public Git repo: Status update

2011-01-11 Thread Yawar Amin
Hi John, Trying to understand your suggestion. Questions below: On 2011-01-08, at 17:16, John Ralls wrote: > […] > > Maybe instead you could create a fake-master branch off of master in your > git-svn repo and tie fake-master to github's master. You mean: [git-svn master] git checkout -b fak

Re: Public Git repo: Status update

2011-01-08 Thread John Ralls
On Jan 8, 2011, at 1:41 PM, Yawar Amin wrote: > Hi, > > On 2011-01-07, at 23:56, John Ralls wrote: > >>> […] >> >> I've moved you into the "owners" group. Do what you will. > > Thanks. I’ve pushed a new gnucash repository, as well as a gnucash-docs > repository. > >> I've attached the autho

Re: Public Git repo: Status update

2011-01-08 Thread Yawar Amin
Hi, On 2011-01-07, at 23:56, John Ralls wrote: >> […] > > I've moved you into the "owners" group. Do what you will. Thanks. I’ve pushed a new gnucash repository, as well as a gnucash-docs repository. > I've attached the authors file I made. If you reimport from svn it will match > up svn acc

Re: Public Git repo: Status update

2011-01-07 Thread John Ralls
On Jan 7, 2011, at 8:40 PM, Yawar Amin wrote: > Hi, > > On 2011-01-07, at 16:41, John Ralls wrote: > >> […] >> >> Meanwhile, I see that Yawar has pushed his own git svn import onto the >> Github repo and also pushed a commit in a new, rather weirdly-named branch. >> Yawar, since you have the

Re: Public Git repo: Status update

2011-01-07 Thread Yawar Amin
Hi, On 2011-01-07, at 16:41, John Ralls wrote: > […] > > Meanwhile, I see that Yawar has pushed his own git svn import onto the Github > repo and also pushed a commit in a new, rather weirdly-named branch. Yawar, > since you have the svn data that goes with that import, you've bought keeping

Re: Public Git repo: Status update

2011-01-07 Thread John Ralls
On Jan 5, 2011, at 5:58 PM, John Ralls wrote: > > On Jan 5, 2011, at 11:01 AM, Derek Atkins wrote: > >> John Ralls writes: >> >>> I also started a straight git svn clone, which stopped mysteriously >>> about the same place. I just restarted it. >> >> What's the bottleneck in doing the conver

Re: Public Git repo: Status update

2011-01-05 Thread John Ralls
On Jan 5, 2011, at 11:01 AM, Derek Atkins wrote: > John Ralls writes: > >> I also started a straight git svn clone, which stopped mysteriously >> about the same place. I just restarted it. > > What's the bottleneck in doing the conversion? This time I kept a tee-file of the output, but I didn

Re: Public Git repo: Status update

2011-01-05 Thread Derek Atkins
John Ralls writes: > On Jan 5, 2011, at 2:29 AM, Christian Stimming wrote: > >> Am Dienstag, 4. Januar 2011 schrieb John Ralls: >>> The second try stopped at r15521 for reasons that aren't entirely clear to >>> me. >> >> This particular revision has nothing uncommon at all. I wouldn't understand

Re: Public Git repo: Status update

2011-01-05 Thread John Ralls
On Jan 5, 2011, at 2:29 AM, Christian Stimming wrote: > Am Dienstag, 4. Januar 2011 schrieb John Ralls: >> The second try stopped at r15521 for reasons that aren't entirely clear to >> me. > > This particular revision has nothing uncommon at all. I wouldn't understand > why git-svn stops partic

Re: Public Git repo: Status update

2011-01-05 Thread Christian Stimming
Am Dienstag, 4. Januar 2011 schrieb John Ralls: > The second try stopped at r15521 for reasons that aren't entirely clear to > me. This particular revision has nothing uncommon at all. I wouldn't understand why git-svn stops particularly there. There are other SVN revisions which cause occasiona

Re: Public Git repo: Status update

2011-01-04 Thread Yawar Amin
Hi John, On 2011-01-04, at 15:11, John Ralls wrote: > […] > > In trying to find out, I read to the bottom of the git-svn man page, where I > found a section called "Caveats". The first paragraph says: >> For the sake of simplicity and interoperating with a less-capable system >> (SVN), it is r

Re: Public Git repo: Status update

2011-01-04 Thread John Ralls
The second try stopped at r15521 for reasons that aren't entirely clear to me. Trying to get it to go further with git svn rebase are met with an error message: Unable to determine upstream SVN information from working tree history. I still don't know what that means. In trying to find out, I