"'Christopher W. Ryan' via Git for human beings"
<git-users@googlegroups.com> writes:
That sounds reasonable. Adding the developing customized
versions as
tracked files in my repo?
Yes, exactly.
/M
mag...@therning.org wrote:
"'Christopher W. Ryan' via Git for human beings"
<git-users@googlegroups.com> writes:
Hello. I'm still just a novice with git. I have a private,
one-person
account on Atlassian's Bitbucket. I use it to manage academic
writing
(usually LaTeX source files.) My usual workflow is to write a
manuscript, then revise revise revise, and eventually get it
into
acceptable shape. I commit along the way in that process.
Eventually I have it pretty much how I like it. But it still
needs
little tweaks to suit particular journals. I'd like to
preserve what
might be called the "core" version, and then spin off versions
customized for submission to different journals.
Journals often reject submissions, of course, so I need to
spin off
from the core a customized version for Journal A, then perhaps
later
spin off from "core" a customized version for Journal B, and
then
again for Journal C, and so on.
I have some experience with branching, where I make
substantial
revisions. But eventually I usually merge the changes back
into
master. Here I would not--I don't expect I'd ever merge the
Journal A
version back into the "core," nor into any other
journal-customized
version.
What would be the best approach to this?
I have no experience with forking but am willing to learn.
For this use case I wouldn't bother with branches. Once you've
arrived
at a core version, then I'd suggest you simply create a folder
for each
customised version, copy the core in and then customise as
needed.
/M
--
Magnus Therning OpenPGP: 0x927912051716CE39
email: mag...@therning.org
@magthe@mastodon.technology http://magnus.therning.org/
`In those days spirits were brave, the stakes were high, men were
REAL
men, women were REAL women, and small furry creatures from Alpha
Centauri were REAL small furry creatures from Aplha Centauri.'
— The Book getting all nostalgic.
--
You received this message because you are subscribed to the Google Groups "Git for
human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/git-users/87wmxtahuj.fsf%40therning.org.
