From: Yuval Hager <yuval@avramzon.net>
To: emacs-orgmode@gnu.org
Subject: Re: Article: Synchronizing org Files Using bzr and git
Date: Wed, 11 Mar 2009 17:19:45 +0200 [thread overview]
Message-ID: <200903111719.45738.yuval@avramzon.net> (raw)
In-Reply-To: <49B0FBFB.7030207@manor-farm.org>
[-- Attachment #1.1: Type: text/plain, Size: 1658 bytes --]
On Friday 06 March 2009, Ian Barton wrote:
> > First of all, I do not control in any way what gets on Worg.
> > Bastien set up Worg as user-edited content, and this is what
> > it should be.
> >
> > If you aks my opinion, I think your tutorial is *exactly* what
> > Worg was made for! I have not studied it in detail, but
> > it looks useful, addresses a subject that has almost become
> > a FAQ. And if it is up on Worg, bugs will be fixed
> > and improvements made.
> >
> > So please feel free to add your tutorial to Worg.
> > The best place would be the org-tutorial directory, and
> > you should then make a link from the index.org in that
> > same directory. After pushing, it will take 1.5 hours or
> > less to appear on the web.
>
> OK, it's now on Worg.
>
I can't find it (I'm rather new to all this).
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).
--
yuval
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 204 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2009-03-11 15:20 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 [this message]
2009-03-11 16:39 ` Ian Barton
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=200903111719.45738.yuval@avramzon.net \
--to=yuval@avramzon.net \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).