Re: [git-users] Any writers out there?

[Gergely Polonkai]

If you decide to commit after each save, you may like SparkleShare. It uses git 
as a backend, and does exactly this, makes a commit whenever anything changes 
in the directory. It feels a bit like a Dropbox, except it's not in the cloud 
(well, unless your git repo is in the cloud).


On 2011.02.28., at 21:43, "mark (my words)"  wrote:

> That's an interesting take. How would one go about using Dropbox for revision 
> control? I have an account softlinked to my writing directories, comes in 
> handy for snagging files when I'm without my laptop.
> 
> I think there might be a cultural divide here. Many developers don't 
> understand how writers write and many writers don't know anything about 
> development. There is an overlap, however, and within that you have folks 
> like Cory Doctorow, and Scott Chacon, it's amazing how many people use geek 
> tools to make poetry and novels and things.
> 
> (Way off topic here, sorry…The best writers I know are on the tech side. Tim 
> Bray for instance, blows me away with his thoughtful, clear, and inciting 
> writing—everyone should read ongoing.)
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Git for human beings" group.
> To post to this group, send email to git-users@googlegroups.com.
> To unsubscribe from this group, send email to 
> git-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/git-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] Any writers out there?

[mark (my words)]

That's an interesting take. How would one go about using Dropbox for 
revision control? I have an account softlinked to my writing directories, 
comes in handy for snagging files when I'm without my laptop.

I think there might be a cultural divide here. Many developers don't 
understand how writers write and many writers don't know anything about 
development. There is an overlap, however, and within that you have folks 
like Cory Doctorow, and Scott Chacon, it's amazing how many people use geek 
tools to make poetry and novels and things.

(Way off topic here, sorry…The best writers I know are on the tech side. Tim 
Bray for instance, blows me away with his thoughtful, clear, and inciting 
writing—everyone should read ongoing .)

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] Any writers out there?

[mark (my words)]

I think that's a good idea. I'm a passionate writer who occasionally looses 
a perfect line in the heat of the moment. Thanks to git I was able to find 
one: I knew I had the perfect description of an abstract emotional construct 
*somewhere, *I knew vaguely where but it wasn't in any of my current 
stories. I was able to go through my git repositories and find it—according 
to the comments I made at the time I had thought it was a throw-away line, 
I'm very happy to have found it.

You're right about history becoming a nightmare to wade through, thanks for 
the code, that's gonna come in handy, that's going in my saved code snippets 
file.

  

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] Any writers out there?

[mark (my words)]

That is a cool article, thanks for posting it.
I love the stash function.


-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] Any writers out there?

[gitent_scm gitent_scm]

Hi,

Please apologize me if I'm going off-topic, first post here and I don't have
the full history :)

I don't know much about writing books, but when you're delivering software
it's definitely useful to track with a single commit a set of changes across
different files. For example
- it's extremely useful to associate to a single commit a bug fix, so that
you can cherry-pick it and reapply later on another branch, without
bothering too much about which files you touched to solve it.
- it's also a good idea to mark with separate commit the different
engineering tasks related to a feature, so that you can track the progress
to reach the full feature and you can associate to a feature a set of
commits

If you just need multiple version of the same file (for example your book)
you may want to use dropbox: it's free, and it's doing exactly this job (and
much more) (and no, I'm not involved with dropbox :D)

Cheers,

B.

-- 
http://www.gitenterprise.com
Git delivered to the Enterprise!
Get a 1Gb/10 users free account now



On Mon, Feb 28, 2011 at 1:59 AM, Charles Manning wrote:

> Why not commit every time you save?
>
> Anyone who worked in the 1980s using VAX would tell you how great it was
> that
> thefile system kept versions of the file. Much, much better than the single
> file version we have now.
>
> There is absolutely nothing wrong with doing work in progress commits after
> every save,
>
> That will make a hell of a history though so you probably want to clean up
> whenever you get to a milestone or before you push. That can be achieved
> with
>
> git reset -- soft 25252 <- last commit that you actually want to keep
> git commit
>
>
>
> On Wednesday 09 February 2011 09:06:33 Anas Mughal wrote:
> > You definitely do not want a commit every time you save your file. Just
> > commit when you reach a milestone, etc.
> >
> > Also, have you looked into using a online document hosting service like
> > GoogleDocs. I presume you need to use advanced editing features that are
> > available part of Word or some other thick client tool.
> >
> > Best Regards.
> >
> > On Mon, Feb 7, 2011 at 6:16 PM, Mark (my words) 
> wrote:
> > > Thanks for all the advice. I’ll apologize upfront for not crediting
> each
> > > of you for your individual contributions in my response—I’m feeling a
> bit
> > > overwhelmed.
> > >
> > > I just made a repository of 23 directories of poems, and yeah, it’s
> > > unwieldy. Thanks for the info on multi-repository tools that will come
> in
> > > handy.
> > >
> > > Too many commits do get out of hand quickly, I should save commits for
> > > those breakthrough moments in a project, not when I just change a
> > > comma—unless it’s an extremely important comma, in which case it better
> > > be commented.
> > >
> > > It just hit me, in my current workflow file names serve as comments I’m
> > > working on a file called /ladybug/ladybug new 3 past tense.markdown:
> that
> > > shows me the branch, version, and the major change: The third version
> of
> > > a new branch in which I move to the past tense.
> > >
> > > *Git compares lines:* I just diff’ed versions of a poem and wondered
> why
> > > it appeared I had deleted a block and replaced it with an identical
> > > block.
> > >
> > > I appreciate the git-show code, but I’m looking for a batch operation,
> > > but that’s best addressed in another post which I’ll make here in a few
> > > minutes.
> > >
> > > I’m moving toward a stripped down all text workflow using minimal
> > > text-editors, open/libre/neo-office is a bit…full-featured…for my
> sanity.
> > >
> > > I need to rethink my organization structure. My short-stories are
> > > arranged by series, but my poems are scattered about under whichever
> > > parent directory grabs my attention at the time—they’re in this order
> of
> > > priority, level of surrealism, emotional content right now and I find
> > > them by openmeta tags (which, yeah, can be convenient until you start
> > > using git).
> > >
> > > *Don’t have chaos:* I like that. I’m happy I decided to address my
> issues
> > > upfront instead of waiting until I went into production with it, these
> > > are some amazing insights you guys have, it saves me from walking
> blindly
> > > into a mine-field! I like the idea of a local master with local
> > > individual repos. It’s gonna take me a while to find a good balance to
> > > fit my needs.
> > >
> > > Wow, this has been the most fun I have ever had in a tech forum. You
> guys
> > > should form a comic troupe.
> > >
> > > Thanks for the wonderfully detailed and insightful comments,
> > >
> > > Mark
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To post to this group, send email to git-users@googlegroups.com.
> To unsubscribe from this group, send email to
> git-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/git-users?hl=en.
>
>

-- 
You received this 

Re: [git-users] Any writers out there?

[Charles Manning]

Why not commit every time you save?

Anyone who worked in the 1980s using VAX would tell you how great it was that 
thefile system kept versions of the file. Much, much better than the single 
file version we have now.

There is absolutely nothing wrong with doing work in progress commits after 
every save,

That will make a hell of a history though so you probably want to clean up 
whenever you get to a milestone or before you push. That can be achieved with 

git reset -- soft 25252 <- last commit that you actually want to keep
git commit



On Wednesday 09 February 2011 09:06:33 Anas Mughal wrote:
> You definitely do not want a commit every time you save your file. Just
> commit when you reach a milestone, etc.
>
> Also, have you looked into using a online document hosting service like
> GoogleDocs. I presume you need to use advanced editing features that are
> available part of Word or some other thick client tool.
>
> Best Regards.
>
> On Mon, Feb 7, 2011 at 6:16 PM, Mark (my words)  wrote:
> > Thanks for all the advice. I’ll apologize upfront for not crediting each
> > of you for your individual contributions in my response—I’m feeling a bit
> > overwhelmed.
> >
> > I just made a repository of 23 directories of poems, and yeah, it’s
> > unwieldy. Thanks for the info on multi-repository tools that will come in
> > handy.
> >
> > Too many commits do get out of hand quickly, I should save commits for
> > those breakthrough moments in a project, not when I just change a
> > comma—unless it’s an extremely important comma, in which case it better
> > be commented.
> >
> > It just hit me, in my current workflow file names serve as comments I’m
> > working on a file called /ladybug/ladybug new 3 past tense.markdown: that
> > shows me the branch, version, and the major change: The third version of
> > a new branch in which I move to the past tense.
> >
> > *Git compares lines:* I just diff’ed versions of a poem and wondered why
> > it appeared I had deleted a block and replaced it with an identical
> > block.
> >
> > I appreciate the git-show code, but I’m looking for a batch operation,
> > but that’s best addressed in another post which I’ll make here in a few
> > minutes.
> >
> > I’m moving toward a stripped down all text workflow using minimal
> > text-editors, open/libre/neo-office is a bit…full-featured…for my sanity.
> >
> > I need to rethink my organization structure. My short-stories are
> > arranged by series, but my poems are scattered about under whichever
> > parent directory grabs my attention at the time—they’re in this order of
> > priority, level of surrealism, emotional content right now and I find
> > them by openmeta tags (which, yeah, can be convenient until you start
> > using git).
> >
> > *Don’t have chaos:* I like that. I’m happy I decided to address my issues
> > upfront instead of waiting until I went into production with it, these
> > are some amazing insights you guys have, it saves me from walking blindly
> > into a mine-field! I like the idea of a local master with local
> > individual repos. It’s gonna take me a while to find a good balance to
> > fit my needs.
> >
> > Wow, this has been the most fun I have ever had in a tech forum. You guys
> > should form a comic troupe.
> >
> > Thanks for the wonderfully detailed and insightful comments,
> >
> > Mark


-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] Any writers out there?

[Bryce Verdier]

I just found this yesterday, not sure how much it'll help, but it is 
related.


http://www.developer.com/open/10-ways-git-version-control-can-streamline-your-writing-projects.html

On 02/07/2011 12:31 PM, Mark (my words) wrote:

Hello,

I'm new to git. I'm trying to develop a workflow for my creative 
writing. I figure that other's must have came before me, so why 
reinvent the wheel?


*Here are some issues I'm dealing with*

/Stay out of the way/how often to commit./
I can use launchd on OS X to call a script to make commits 
periodically and/or when a file changes. Is making a commit every time 
a file is saved too much? (I tend to save a bunch.)


/Should I have multiple git repositories or a single monolithic one?/
I usually have several projects in the works, each individual piece 
(poem, story) has it's own directory which I use to keep working drafts.
I'd hate to have to remember to run git init, git add . , and setup a 
laucnhd script, every time I start a new poem, but I would also hate 
to be overwhelmed by navigating a huge repository.


/Is it possible to save out multiple versions of a single file? (easily?)/
I often need to open three, four, or more versions of a file. And I 
occasionally need to print several old versions. Can git do this? I 
know I can use diff to compare two versions, and I can open a 
particular version, is it possible to open/save the last n versions of 
a file?


/Is git for me?/
Am I running into a fundamental incompatibility problem? Do I just 
need to learn more about git? What are some good resources to look 
at—I'm overwhelmed by the sheer number of git articles online.



Thanks,


Mark
--
You received this message because you are subscribed to the Google 
Groups "Git for human beings" group.

To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.


--
You received this message because you are subscribed to the Google Groups "Git for 
human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] Any writers out there?

[Mark (my words)]

No worries, my TW backups are in an entirely differnt directory structure 
from my writing—that would be a mess.

Git may not be an appropriate tool, I guess that’s what I’m trying to 
discover. I go through an unholy number of drafts—it can be a hassle 
tracking down that one phrase that didn’t make an earlier cut but is now 
perfect for the current revision.

There are fits and starts and regressions and spurts of inspiration followed 
by doubt. I need something to keep me from being burried under a mountain of 
drafts—while keeping them available, that gives me the courage to move 
forward, and affords me not to be in a constant state of panic of loosing 
that that perfect phrase.

I’m currently working on three different branches of a single poem. I know 
something’s there, but the narritive mode is freaking me out—I may have 
stumble on a tense heretofore unknown in English :) Digging through the 
drafts and picking out the three I want to work on at any given time is a 
pain.

So far git is proving valuable, but I won’t know until I complete a full 
project with it.

Oh, that’s right. I bookmarked that book the other day and haven’t got back 
to it, I’m glad you reminded me.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] Any writers out there?

[Sam Sherlock]

make sure you have .gitignore to NOT TRACK you text wrangler backup files

google docs does not support git AFAIK - not sure if git is the most
appropriate tool
for managing written word collection (could really depend on the User)

but it is very accommodating ; the book I recommended used a peom as example
text
but I think this was an example selected for its simplicty perfect for
introduction
to using the tool.

it might be absolutly perfect for what you need
 - S



On 9 February 2011 03:37, Brett Viren  wrote:

> On Mon, Feb 7, 2011 at 9:16 PM, Mark (my words)  wrote:
>
> > Git compares lines: I just diff’ed versions of a poem and wondered why it
> > appeared I had deleted a block and replaced it with an identical block.
>
> Maybe a whitespace only change was made.  You could re-try with
>
>  git-diff -w
>
> -Brett.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To post to this group, send email to git-users@googlegroups.com.
> To unsubscribe from this group, send email to
> git-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/git-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] Any writers out there?

[Brett Viren]

On Mon, Feb 7, 2011 at 9:16 PM, Mark (my words)  wrote:

> Git compares lines: I just diff’ed versions of a poem and wondered why it
> appeared I had deleted a block and replaced it with an identical block.

Maybe a whitespace only change was made.  You could re-try with

 git-diff -w

-Brett.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] Any writers out there?

[Mark (my words)]

You definitely do not want a commit every time you save your file. Just 
commit when you reach a milestone, etc.

Good deal. I'm still experimenting with that. Some of my projects a single 
line, or word, change is a major milestone. But it looks like I'll be 
manually committing to git and relying on TextWranglers autobackup on save 
feature for smaller changes. There seems to be a fine line there somewhere, 
and a huge gap between my vision and ability—but it's getting smaller

Also, have you looked into using a online document hosting service like 
GoogleDocs. I presume you need to use advanced editing features that are 
available part of Word or some other thick client tool.

Does GoogleDocs handle git repositories? Or are you suggesting an 
alternative to using git?

No, I don't use or need word-processors. I have a raw text workflow. I 
mainly use TextWrangler and vim; writing in MultiMarkdown or other 
lightweight markup languages. For rendered text I run it through Mmd or 
Pandoc. I'm growing more accustomed to LaTex and hope to use it more in the 
future.

Once I have my workflow down I'm going to install git on my webhosting 
service or seek out a semi-privite hosted repository. I would like to allow 
people to browse my changes or not to alter content.


All Best,

Mark

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] Any writers out there?

[Anas Mughal]

You definitely do not want a commit every time you save your file. Just
commit when you reach a milestone, etc.

Also, have you looked into using a online document hosting service like
GoogleDocs. I presume you need to use advanced editing features that are
available part of Word or some other thick client tool.

Best Regards.




On Mon, Feb 7, 2011 at 6:16 PM, Mark (my words)  wrote:

> Thanks for all the advice. I’ll apologize upfront for not crediting each of
> you for your individual contributions in my response—I’m feeling a bit
> overwhelmed.
>
> I just made a repository of 23 directories of poems, and yeah, it’s
> unwieldy. Thanks for the info on multi-repository tools that will come in
> handy.
>
> Too many commits do get out of hand quickly, I should save commits for
> those breakthrough moments in a project, not when I just change a
> comma—unless it’s an extremely important comma, in which case it better be
> commented.
>
> It just hit me, in my current workflow file names serve as comments I’m
> working on a file called /ladybug/ladybug new 3 past tense.markdown: that
> shows me the branch, version, and the major change: The third version of a
> new branch in which I move to the past tense.
>
> *Git compares lines:* I just diff’ed versions of a poem and wondered why
> it appeared I had deleted a block and replaced it with an identical block.
>
> I appreciate the git-show code, but I’m looking for a batch operation, but
> that’s best addressed in another post which I’ll make here in a few minutes.
>
> I’m moving toward a stripped down all text workflow using minimal
> text-editors, open/libre/neo-office is a bit…full-featured…for my sanity.
>
> I need to rethink my organization structure. My short-stories are arranged
> by series, but my poems are scattered about under whichever parent directory
> grabs my attention at the time—they’re in this order of priority, level of
> surrealism, emotional content right now and I find them by openmeta tags
> (which, yeah, can be convenient until you start using git).
>
> *Don’t have chaos:* I like that. I’m happy I decided to address my issues
> upfront instead of waiting until I went into production with it, these are
> some amazing insights you guys have, it saves me from walking blindly into a
> mine-field! I like the idea of a local master with local individual repos.
> It’s gonna take me a while to find a good balance to fit my needs.
>
> Wow, this has been the most fun I have ever had in a tech forum. You guys
> should form a comic troupe.
>
> Thanks for the wonderfully detailed and insightful comments,
>
> Mark
>
> --
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To post to this group, send email to git-users@googlegroups.com.
> To unsubscribe from this group, send email to
> git-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/git-users?hl=en.
>



-- 
Anas Mughal

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] Any writers out there?

[Mark (my words)]

Thanks for all the advice. I’ll apologize upfront for not crediting each of 
you for your individual contributions in my response—I’m feeling a bit 
overwhelmed.

I just made a repository of 23 directories of poems, and yeah, it’s 
unwieldy. Thanks for the info on multi-repository tools that will come in 
handy.

Too many commits do get out of hand quickly, I should save commits for those 
breakthrough moments in a project, not when I just change a comma—unless 
it’s an extremely important comma, in which case it better be commented.

It just hit me, in my current workflow file names serve as comments I’m 
working on a file called /ladybug/ladybug new 3 past tense.markdown: that 
shows me the branch, version, and the major change: The third version of a 
new branch in which I move to the past tense.

*Git compares lines:* I just diff’ed versions of a poem and wondered why it 
appeared I had deleted a block and replaced it with an identical block.

I appreciate the git-show code, but I’m looking for a batch operation, but 
that’s best addressed in another post which I’ll make here in a few minutes.

I’m moving toward a stripped down all text workflow using minimal 
text-editors, open/libre/neo-office is a bit…full-featured…for my sanity.

I need to rethink my organization structure. My short-stories are arranged 
by series, but my poems are scattered about under whichever parent directory 
grabs my attention at the time—they’re in this order of priority, level of 
surrealism, emotional content right now and I find them by openmeta tags 
(which, yeah, can be convenient until you start using git).

*Don’t have chaos:* I like that. I’m happy I decided to address my issues 
upfront instead of waiting until I went into production with it, these are 
some amazing insights you guys have, it saves me from walking blindly into a 
mine-field! I like the idea of a local master with local individual repos. 
It’s gonna take me a while to find a good balance to fit my needs.

Wow, this has been the most fun I have ever had in a tech forum. You guys 
should form a comic troupe.

Thanks for the wonderfully detailed and insightful comments,

Mark

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] Any writers out there?

[Brett Viren]

On Mon, Feb 7, 2011 at 3:31 PM, Mark (my words)  wrote:

> I'm new to git. I'm trying to develop a workflow for my creative writing.

FWIW, I use git for just about every document I produce (report,
paper, presentation).  Most of the text is in LaTeX, notes using
emacs's dot.org mode and sometime figures or pictures.  I have one
repo per "project" which is sometimes loosely defined.  I don't use
git submodules or similar but I do factor out some files to a "common"
project (eg logos that get reused in many presentations).

Even if I'm the only author it is useful to commit at points like
"first draft", "draft for initial comments", "comments from Fred
addressed", "final draft", "final final draft" and "final final final
dammit I mean it this time draft", etc.

When I collaborate on a document I find it essential to put it in git
(or other VC).  Even if the other user doesn't use git (or other VC)
it is helpful to track the contributions they feed you and avoid
inadvertently stomping on text that they have modified.

I agree with the others that auto-commits would give more problems
than help as you wouldn't know which commit was meaningful.  I guess
you could label all auto commits with an empty message and then look
for manual commits with a more meaningful comment (or with an explicit
tag) but it's kind of a stretch.

For your poems, if they tend to be short, I'd probably come up with
some kind of collection rule and put each one in its own repo (eg. all
cute bunny poems separate from all self-critical introspections).

Oh, and one thing to be mindful of is text lines, particularly if you
are using an unformatted source (like LaTeX, HTML, etc).  Git wants to
compare based on lines so make them as short and atomic as possible.
Do try to use line breaks and not long monolithic lines as it makes
comparing differences that much easier.  This matters a lot when you
need to merge two versions (eg two branches or incorporating stuff
being fed by had from collaborators).

-Brett.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Re: [git-users] Any writers out there?

[Sam Sherlock]

> *how often to commit.*
>

I would'nt automate commits; I would not commit with every save

A commit is a piece of progress you commit when you see that it works;  but
you can't ensure that nothing else breaks due to what you have changed.  So
when you later notice that something is broken and want to find out at which
point
the breaking occured small focused commited with clear messages are helpful
(if you working solo then after a few months revisting code can still seem
alien)

git flow is very helpful in assisting with workflow

it maintains branches for specific tasks; eg bug fixing, feature creation
and releases

say you are making a site that is working pefectly in all browsers but not
IE

and you have created a branch which focuses on resolving the IE issues.  You
can continue to make progress on other features since you are
uninspred/reluctant to make the ie issues go away.

the ie-fix branch has an alteration to the readme and todo marker comments
in various places within the source (you have painstakingly code that is
part of the problem but have not decided upon the correct solution as yet)

The newly developed features get merged into the ie-fix branch so that it is
not left behind the production site (which does not have extensive comments
where you curse Gates, Balmer et al) At some point try an idea to resolve
soe ie issues and notice that other issue have resolved themselves YAY.  You
then manage to fix it pinning things down to a point where you know the
exact piece of code that either fixes or causes the issue - the one that
fixes it is a commit.

the files changed are various html and css files (there is another issue you
have spotted - but it remains in the repo and you note it down on paper -
its another commit not the focus of this branch implementing it not
contaminates the commit)

"Solved IE Css formating issue; had to use these wierd css hacks and in
addition have various divs for wrapping content just for IE" (you then solve
a few more things which you have noted as different issues - each of these
is its own commit)

these commits can be cherry-picked in to your master (tagging master so that
if other issue arise from these fixes you have a starting point resolving
these issues)

this way you don't find yourself in a situation where you notice 6 issues
and don't know at what phaze of development youwent wrong.


>
> *Should I have multiple git repositories or a single monolithic one?*
>

don't have chaos; I am recovering from a chaotic setup dating back to when I
was starting out with git

what I am trying to get to (this seems to work well):
Have repos on github
Have a master local repo (push from this to github)
Have local repos (these can pull direct from the local master; and the local
master can pull from it - NOT PUSHING - that would mess things up)

temp repos set something up get it to do what you need; test out things; if
you mess it up delete if its good
PLAN how to merge the updates in to master-local and push to www-repo


>
> *Is it possible to save out multiple versions of a single file? (easily?)*
>
>
so you have multiple variation of the same project; just branch the changes

git checkout -b newBranch [basedUpon]


> *Is git for me?
>
> *
>

its a life - changer for many; it means I can be more productive; I don't
need to have an insane bewildering collection of tars; I can use gitk to
walkthrough the history of my code and then pop right back to the future

git is my DMC 12 and that makes me Marty McFly

as for tutorials
github.com have a wealth of documentation and its really clear informative
stuff
they have a site with videos too (Scott Chacon)
http://git-scm.com/documentation

lots of people come to git from svn, I never did get on with SVN (or any
visioning control*),
searching for git for SVN users may be helpful if you are familiar with SVN


Get a book or two.  I got an O'Reily Press one with Bat on the front

ProGit is one that I have much good things about;
and also Travis Swicegoods book also

* I never got on with visioning code and had to perform intense and
labourous task to be able to revert to a stage when the project was working
better than it is currently since these improvements turned out to be false
hope.

Now when I need to revert a project I can do so with a few lines  in the
console and all is right again and I can make a new attempt to implement
those improvements - without the chore and NULL time spent regressing
through archives or getting on with SVN in a civil manner

git is a simple solution to problem that other proposed solutions have often
proved to be more complex than what they set out to solve.

git it straight from the source :)
http://www.youtube.com/watch?v=4XpnKHJAok8

On 7 February 2011 20:31, Mark (my words)  wrote:

> Hello,
>
> I'm new to git. I'm trying to develop a workflow for my creative writing. I
> figure that other's must have came before me, so why reinvent the wheel?
>
> *Here are some issues I'm dealing wit

[git-users] Any writers out there?

[Mark (my words)]

Hello, 

I'm new to git. I'm trying to develop a workflow for my creative writing. I 
figure that other's must have came before me, so why reinvent the wheel?

*Here are some issues I'm dealing with*

*Stay out of the way/how often to commit.*
I can use launchd on OS X to call a script to make commits periodically 
and/or when a file changes. Is making a commit every time a file is saved 
too much? (I tend to save a bunch.)

*Should I have multiple git repositories or a single monolithic one?*
I usually have several projects in the works, each individual piece (poem, 
story) has it's own directory which I use to keep working drafts.
I'd hate to have to remember to run git init, git add . , and setup a 
laucnhd script, every time I start a new poem, but I would also hate to be 
overwhelmed by navigating a huge repository.

*Is it possible to save out multiple versions of a single file? (easily?)*
I often need to open three, four, or more versions of a file. And I 
occasionally need to print several old versions. Can git do this? I know I 
can use diff to compare two versions, and I can open a particular version, 
is it possible to open/save the last n versions of a file?

*Is git for me?*
Am I running into a fundamental incompatibility problem? Do I just need to 
learn more about git? What are some good resources to look at—I'm 
overwhelmed by the sheer number of git articles online.


Thanks,


Mark

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.