..." to include in what will be committed) # # next-actions.nothing added to commit but untracked files present (use "git add" to track) $ git add next-actions.$ git commit -m 'getting started' [master (root-commit)]: created e98f811: "getting started" 1 files changed, 4 insertions( ), 0 deletions(-) create mode 100644 next-actions.$ git log commit e98f811b6b67ffd354ff33ef5df3da872a8e7059 Author: William Denton $ cd york $ git clone picketfence:york/gtd/ Initialized empty Git repository in /home/buff/york/gtd/.git/ remote: Counting objects: 3, done. remote: Total 3 (delta 0), reused 0 (delta 0) Receiving objects: 100% (3/3), 268 bytes, done.$ git commit -m 'update' next-actions.[master]: created 15f2969: "update" 1 files changed, 1 insertions( ), 0 deletions(-) $ git status # On branch master # Your branch is ahead of 'origin/master' by 1 commit. Total 3 (delta 0), reused 0 (delta 0) warning: updating the currently checked out branch; this may cause confusion, as the index and working tree do not reflect changes that are now in HEAD.This is handled by reverse adjusting commits one at a time and rebasing the others on top.
To manage the GTD files I settled on outline mode, which is built into Emacs. Here's an example of mine: * E-mail ** Catherine: accurate collection stats for Wikipedia entry ** LCC: will be away for next meeting ** Peter R: is Joomla in use anywhere at York?
If so, could I get a test account to see what it's like?
I use the Getting Things Done system to keep track of what I'm doing. My personal stuff I keep track of in paper in a Filofax, but I have a lot more detail to track at work at York University, so I use text files. I have three files to manage what I'm doing, plus a monthly work diary: (I'll explain about Emacs and outline mode below.) I use the distributed version control system git to manage these files.
First, I set up a basic repository on a Unix host where I do my personal e-mail.
remote: error: remote: error: You can set 'Delete Current' configuration variable to remote: error: 'warn' or 'ignore' in the remote repository to allow deleting the remote: error: current branch, with or without a warning message.
remote: error: remote: error: To squelch this message, you can set it to 'refuse'.They're not in the cloud so I can work on them without Internet access.I'm a Unix-loving geek, so of course I keep my text in text files.remote: error: refusing to delete the current branch: refs/heads/master To [email protected]:/export/home/a/elabshare/git/![remote rejected] master (deletion of the current branch prohibited) error: failed to push some refs to '[email protected]:/export/home/a/elabshare/git/ID-check.git' Fun fact: even remote repositories are on a branch. For #2 above it would omit files whose content is not currently in the annex. The function is currently implemented as the git-annex-adjust command.