emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Pieter Praet <pieter@praet.org>
To: Jude DaShiell <jdashiel@shellworld.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: git useage question
Date: Sun, 05 Jun 2011 02:06:36 +0200	[thread overview]
Message-ID: <877h91rvjn.fsf@praet.org> (raw)
In-Reply-To: <alpine.BSF.2.00.1106041925140.11604@freire1.furyyjbeyq.arg>

On Sat, 4 Jun 2011 19:26:54 -0400 (EDT), Jude DaShiell <jdashiel@shellworld.net> wrote:
> 1) so we understand each other.  My complaint has nothing to do with 
>    org-mode's documentation and everything to do with the documentation 
>    for git itself. [...]

Oh, I see :D

So your query should have been directed to the git mailing list [1],
but I admit that whether it would've garnered any useful responses is
rather doubtful.


Assuming you have no prior experience with distributed version control,
the following should be a very clear and concise introduction:
- http://eagain.net/articles/git-for-computer-scientists/
- http://hoth.entp.com/output/git_for_designers.html
- http://www-cs-students.stanford.edu/~blynn/gitmagic/


It's really worth the effort, as it'll pay back in no time.

Very soon you'll wonder how you've ever been able to work without it ;)


> [...] On Sun, 5 Jun 2011, Pieter Praet wrote:
> 
> > On Sat, 4 Jun 2011 18:05:47 -0400 (EDT), Jude DaShiell <jdashiel@shellworld.net> wrote:
> > > I wouldn't be writing this if the documentation were reasonable.  Once 
> > > org-mode gets cloned, how is git properly used to update the cloned 
> > > instance on a machine?
> > 
> > I wouldn't be writing this if your comment were reasonable.
> > 
> > 
> > The following should be more than sufficient:
> >   - http://orgmode.org/manual/Installation.html#Installation
> >   - http://orgmode.org/worg/org-faq.html#Keeping-current
> > 
> > 
> > In the *highly unlikely* case that it isn't:
> >   You're probably already aware of this (though this awareness may be
> >   temporarily impeded due to Saturday night related inebriation), but
> >   it's worth noting that Org-mode's documentation documents Org-mode.
> > 
> >   Org-mode != git, otherwise it would be called git instead of Org-mode, see?
> > 
> >   Kindly refer to some relevant (and extremely abundant) documentation:
> >   - http://git-scm.com/documentation
> > 
> > 
> > Peace
> > 
> > 
> 
> 


Peace


[1] http://dir.gmane.org/gmane.comp.version-control.git

-- 
Pieter

  reply	other threads:[~2011-06-05  0:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-04 22:05 git useage question Jude DaShiell
2011-06-04 22:11 ` Nick Dokos
2011-06-04 22:32   ` Jude DaShiell
2011-06-04 23:17 ` Pieter Praet
2011-06-04 23:26   ` Jude DaShiell
2011-06-05  0:06     ` Pieter Praet [this message]
2011-06-05  1:21     ` Nick Dokos
2011-06-05  2:45       ` Jude DaShiell
2011-06-05 16:40 ` Achim Gratz
  -- strict thread matches above, loose matches on Subject: below --
2011-06-05 10:50 Rustom Mody
2011-06-05 13:27 ` Jude DaShiell

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=877h91rvjn.fsf@praet.org \
    --to=pieter@praet.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=jdashiel@shellworld.net \
    /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).