emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ian Barton <lists@manor-farm.org>
To: Yuval Hager <yuval@avramzon.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Article: Synchronizing org Files Using bzr and git
Date: Wed, 11 Mar 2009 16:39:23 +0000	[thread overview]
Message-ID: <49B7E93B.5000401@manor-farm.org> (raw)
In-Reply-To: <200903111719.45738.yuval@avramzon.net>

> One thing that confused me is that I tried to work with two machines, 
> without a server. Figuring git is distributed, I thought I do not need a 
> server, and I tried to follow the tutorial. Obviously, I got hit when I 
> performed a 'git push' onto a non-bare repository (now I know what these 
> things mean ;).
> I now know not to use 'push' and can get along fine with just 'pull'-ing. I 
> think the tutorial might be better if you either mention how to work 
> without a server, or just put a big note not to push onto a non-server 
> branch (There is a note there, but it was probably not big enough for me ;)
> Thanks for a great tutorial. You made me cross the git barrier. Once I'm on 
> the other side, nothing would take me back (same way I felt about org-mode 
> after seeing Russell Adams' video).


Thanks for the comments. I want to improve the git section. One thing 
that's easy with bzr is to just push your changes to a remote server, or 
a usb stick in one operation, even if the remote repo doesn't exist.

Using git this seems to be problematic. You can't use push unless there 
is a repo already there. You can create a blank repo ready to push into, 
but for the lazy this requires two steps instead on one. It is supposed 
to be possible to use git clone to create the repo and populate in a 
single step. However, I seem to fall into a syntactic black hole here 
and just end up creating a new repo locally.


  reply	other threads:[~2009-03-11 16:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 13:42 Article: Synchronizing org Files Using bzr and git Ian Barton
2009-03-03 18:49 ` Mark Elston
2009-03-04 10:32   ` Ian Barton
2009-03-04 14:37     ` Bernt Hansen
2009-03-04 14:56       ` Carsten Dominik
2009-03-04 15:01       ` Sebastian Rose
2009-03-04 22:21         ` Ian Barton
2009-03-04  6:31 ` Yuval Hager
2009-03-04 11:42 ` Carsten Dominik
2009-03-06 10:33   ` Ian Barton
2009-03-06 15:35     ` Carsten Dominik
2009-03-11 15:19     ` Yuval Hager
2009-03-11 16:39       ` Ian Barton [this message]
2009-03-11 20:20         ` Alan E. Davis
2009-03-04 12:16 ` Cameron Horsburgh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49B7E93B.5000401@manor-farm.org \
    --to=lists@manor-farm.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=yuval@avramzon.net \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).