Hey Harold, I haven't tried out ditz yet for the tickets, but (in case you hadn't seen it yet) there's a "history" link on each github project that will also show you the log. That might be easier than having to always do a "git pull" everytime to check it out,
-tieg On Tue, Apr 15, 2008 at 11:23 AM, Harold Hausman <[EMAIL PROTECTED]> wrote: > Hi why, others. > > I was lightly tracking the development of shoes previously by > occasionally surfing this link: > http://code.whytheluckystiff.net/shoes/timeline > > I liked that because I could watch changes to code, samples, tickets, > etc, all in one place. I'm trying to continue trolling, and I want to > make sure I'm doing it the right way. :) > > (please pardon, and/or correct, any terminology missteps I make here) > I've got git and ditz up and running, and I've cloned the shoes github > repository. Some days later, if I haven't pulled the latest from the > repository and in my shoes directory I do a 'git log' I only see the > old log. (i.e., I seethe log from the last time I did a 'git pull') So > then, when I do a 'git pull' I see lots of new stuff coming from the > repository, and later calls to 'git log' show newer changes. I think > this is good. Is this the closest thing we have to the old trac > timeline? > > Also, if I do a 'git pull' and I get this response: "Already > up-to-date." I'm assuming that means there have been no changes (no > code changes, no sample changes, no ticket changes, etc) since the > last time I did a 'git pull'... Is this correct? > > Thanks in advance for any insight, > -Harold >
